_ registry / mcp http-sse · checked 1h ago

ampworth-calculators

https://ampworth.com

Registry code: 1060b1593f467ebe

api record

Search and read UK guides on solar PV, heat pumps, batteries and MCS certification.

from a public catalogue that lists it, not from the operator

endpoint
https://ampworth.com/mcp/calculators
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is ampworth-calculators live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ampworth-calculators free to use?
Yes — the hub reached it with no key and no payment.
What tools does ampworth-calculators have?
12 tools: heat_pump_noise, heat_pump_running_cost, heat_pump_size, connection_route, hot_water_cylinder, radiator_flow_temperature, room_heat_loss, solar_pv_output, ….
Is ampworth-calculators safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
154ms

last good check

priced tools
0

of 12 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 12 tools
1 open 11 never probed 1 of 12 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_calculators open 1h ago

    Lists every calculator on this server, with the standard behind it and whether it is the whole-system sizing calculator or one of the single-method ones, plus the reference data a caller needs to build a valid request: the compass directions and their orientations, the shading descriptions, the twenty-five solar postcode zones, the eight heat pump design locations with their design temperatures, the room types and their internal design temperatures, the heat loss element kinds, the occupancy archetypes and the fuel types. Call this when a value must be one of a fixed set and you are not sure what the set is.

    mcp-tool

    {
      "type": "object",
      "additionalProperties": false
    }
    arguments 4 lines
  • heat_pump_noise unknown 1h ago

    Calculate the sound pressure level an air source heat pump produces at an assessment position, and whether it meets the 37 dB(A) permitted development noise limit, using the method in MCS 020. The formula is Lp = Lw + 10 log(Q / 4.pi.r^2) - Ab. Lw is the A-weighted sound POWER level of the unit from its product fiche, energy label or the MCS product database. This is not the sound pressure level, which is a smaller number that already has a distance built into it; confusing the two produces an answer that is wrong by about twenty decibels. The figure for low noise mode must not be used. Q is the directivity factor, from the count of reflecting surfaces within one metre of the unit that extend at least a metre past it in two or more directions. The ground counts; vegetation does not. One surface gives Q=2, two gives Q=4, three gives Q=8. More than three cannot meet MCS 020 at all. r is the straight-line distance in metres to the assessment position, which is a window or door of a habitable room in a NEIGHBOURING property, at any floor. Every affected position must be checked separately, and the nearest is not always the worst. Ab is the barrier attenuation. Fences with gaps, and vegetation of any kind, count as no barrier. Where several units serve one position, list them all and they are combined logarithmically. Method from MCS 020. These calculators follow the published MCS methods, for understanding a system and checking a quotation. Anything that gets installed still needs a design and a site survey from a certified installer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "units"
      ],
      "properties": {
        "units": {
          "type": [
            "null",
            "array"
          ],
          "items": {
            "type": "object",
            "required": [
              "soundPowerLevel",
              "distance",
              "reflectingSurfaces"
            ],
            "properties": {
              "label": {
                "type": "string",
                "description": "A name for this unit, for a result covering more than one."
              },
              "distance": {
                "type": "number",
                "description": "Straight-line distance in metres from the centre of the unit to the assessment position, measured to the nearest 0.1 m. Required."
              },
              "barrierType": {
                "type": "string",
                "description": "'type_1' for solid masonry or a solid fence at least 18 mm thick, 'type_2' for a solid fence thinner than 18 mm, or 'none'. Fences with gaps, and vegetation, are 'none'. Defaults to 'none'."
              },
              "lineOfSight": {
                "type": "string",
                "description": "Whether the assessment position can be seen from the top edge of the unit: 'none', 'partial' (visible if you move up to 0.25 m in any direction) or 'full'. Defaults to 'full'."
              },
              "soundPowerLevel": {
                "type": "number",
                "description": "A-weighted sound POWER level of the unit in dB(A), from the product fiche, the energy label or the MCS product database. Not the sound pressure level, which is a different and smaller number. The figure for low noise mode must not be used. Required."
              },
              "reflectingSurfaces": {
                "type": "integer",
                "description": "How many surfaces sit within one metre of the unit and extend at least a metre past it in two or more directions. The ground counts; vegetation does not. 1, 2 or 3. More than 3 fails MCS 020 outright. Required."
              }
            },
            "additionalProperties": false
          },
          "description": "The heat pump or heat pumps being assessed, each with its own distance and barrier to this assessment position. At least one is required."
        }
      },
      "additionalProperties": false
    }
    arguments 51 lines
  • heat_pump_running_cost unknown never probed

    Compare what a household spends heating on its current fuel with what the same heat would cost from a heat pump. The heat demand is worked out from the household's own metered fuel use, not from a model, because a year of bills describes a particular house far better than any estimate of it. Supply the annual fuel use in the fuel's own unit (kWh for gas and electricity, litres for oil and LPG, kilograms for coal), its price per unit in pounds, and the seasonal efficiency of the existing appliance, which defaults to a realistic figure for that fuel instead of the one on the badge. The comparison turns on one ratio. A heat pump costs less to run whenever its seasonal coefficient of performance beats the ratio between the price of a unit of electricity and the price of a unit of heat from the current fuel. The result reports that break-even figure explicitly. SCOP must be the figure at the flow temperature the system is actually designed for. The same machine can return 4.2 at 35 degrees and 3.1 at 55, and quoting the first for a system designed at the second is the commonest way of overstating a saving. This is a running cost comparison. It says nothing about the capital cost or any grant. Method from MCS 007. These calculators follow the published MCS methods, for understanding a system and checking a quotation. Anything that gets installed still needs a design and a site survey from a certified installer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "annualFuelUse",
        "fuelPricePerUnit",
        "scop",
        "electricityPricePerKwh"
      ],
      "properties": {
        "fuel": {
          "type": "string",
          "description": "The fuel being replaced: 'mains_gas', 'oil', 'lpg', 'electricity' or 'coal'. Defaults to 'mains_gas'."
        },
        "scop": {
          "type": "number",
          "description": "Seasonal coefficient of performance of the proposed heat pump: the units of heat it delivers per unit of electricity, averaged over a year at the design flow temperature. Required."
        },
        "annualFuelUse": {
          "type": "number",
          "description": "How much of that fuel the house uses in a year, in the fuel's own unit: kWh for gas and electricity, litres for oil and LPG, kilograms for coal. Take it from a year of bills. Required."
        },
        "fuelPricePerUnit": {
          "type": "number",
          "description": "Price of one unit of that fuel, in pounds. Required."
        },
        "nonHeatingFraction": {
          "type": "number",
          "description": "Share of that fuel used for something other than heating and hot water, such as a gas hob, as a decimal. A hob is usually 0.03 to 0.05. Defaults to 0."
        },
        "applianceEfficiency": {
          "type": "number",
          "description": "Seasonal efficiency of the existing appliance, as a decimal. Defaults to the typical figure for the fuel."
        },
        "electricityPricePerKwh": {
          "type": "number",
          "description": "Price of a unit of electricity, in pounds. Required."
        },
        "fuelStandingChargePerDay": {
          "type": "number",
          "description": "Daily standing charge for that fuel in pounds, if it has one. A house that removes its gas boiler can usually stop paying this."
        },
        "electricityStandingChargePerDay": {
          "type": "number",
          "description": "Daily electricity standing charge in pounds. It is paid either way, so it only changes the answer if the tariff changes with the heat pump."
        }
      },
      "additionalProperties": false
    }
    arguments 48 lines
  • heat_pump_size unknown never probed

    Estimate the heat pump a UK house needs, and what it would cost to run against the fuel it burns now. IMPORTANT: MIS 3005-D requires a heat pump to be sized from a room-by-room heat loss calculation to BS EN 12831, and nothing here replaces that. Say so whenever you report a result from this, and point the user at the room-by-room calculation. What the figure is for is checking whether a size somebody has been quoted is plausible, because oversizing is the commonest fault in heat pump installations and it is invisible to the person living with it. There are two routes and the first is much the better one. From metered fuel, which is preferred: give 'annualFuelUse' from a year of bills. The fuel becomes heat delivered, hot water comes off it using the MIS 3005-D formula, and what remains divided by the local heating degree days gives the building's heat loss coefficient in watts per kelvin. Degree days are computed from the Met Office monthly means published in MGD 007 section 5. From the fabric, as a fallback when there are no bills: give 'floorAreaM2', an 'insulation' level and a 'propertyType'. The watts per kelvin per square metre behind this are a reasonable reading of British housing stock but they are NOT MCS figures, because MCS publishes no such shortcut. Say so when using this route. Either way the peak load is the coefficient multiplied by the design temperature difference for the location, from Table 2 of MIS 3005-D. The heat pump must deliver at least that at the design outside temperature and the design flow temperature, which is not the same as its headline rating. The result also compares what each of four flow temperatures would cost to run, which is the decision that governs the bill and the one a quotation most often leaves unstated. Supply 'quotedHeatPumpKw' to have a quoted size checked against the estimate. Method from MIS 3005-D. These calculators follow the published MCS methods, for understanding a system and checking a quotation. Anything that gets installed still needs a design and a site survey from a certified installer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "location"
      ],
      "properties": {
        "fuel": {
          "type": "string",
          "description": "The fuel the house is heated with now: 'mains_gas', 'oil', 'lpg', 'electricity' or 'coal'. Defaults to 'mains_gas'."
        },
        "scop": {
          "type": "number",
          "description": "Seasonal coefficient of performance of the proposed heat pump, if it is known from the MCS Product Directory. Defaults to an indicative figure for the chosen flow temperature."
        },
        "bedrooms": {
          "type": "integer",
          "description": "Number of bedrooms, for the hot water demand. Defaults to 3."
        },
        "location": {
          "type": "string",
          "description": "Nearest of the eight tabulated locations: 'belfast', 'birmingham', 'cardiff', 'edinburgh', 'glasgow', 'london', 'manchester' or 'plymouth'. Required."
        },
        "occupants": {
          "type": "integer",
          "description": "Number of people living there, if known. MIS 3005-D takes the greater of this and bedrooms plus one."
        },
        "insulation": {
          "type": "string",
          "description": "How well insulated the building is: 'solid', 'cavity_unfilled', 'insulated', 'modern' or 'very_efficient'. Used only with floorAreaM2."
        },
        "designBasis": {
          "type": "string",
          "description": "'a' for the 99% outside design temperature or 'b' for the colder 99.6% one. Defaults to 'a'."
        },
        "floorAreaM2": {
          "type": "number",
          "description": "Total heated floor area in square metres, over all storeys. Used only when no fuel figure is given."
        },
        "internalTemp": {
          "type": "number",
          "description": "Whole-house mean internal design temperature in Celsius. Defaults to 20, which is a reasonable average of the room-by-room figures in MIS 3005-D Table 1."
        },
        "propertyType": {
          "type": "string",
          "description": "'detached', 'semi', 'end_terrace', 'mid_terrace', 'flat' or 'bungalow'. Used only with floorAreaM2. Defaults to 'semi'."
        },
        "annualFuelUse": {
          "type": "number",
          "description": "How much of that fuel the house burns in a year, in its own unit: kWh for gas and electricity, litres for oil and LPG, kilograms for coal. Give this if it is known: it describes the actual house and is far better than the fabric estimate."
        },
        "flowTemperature": {
          "type": "number",
          "description": "The flow temperature the system would be designed around: 35, 45, 50 or 55. Defaults to 45. This is the single biggest influence on running cost."
        },
        "fuelPricePerUnit": {
          "type": "number",
          "description": "Price of one unit of the current fuel, in pounds. Optional; supplying it and the electricity price gives a running cost comparison."
        },
        "quotedHeatPumpKw": {
          "type": "number",
          "description": "The output of a heat pump somebody has quoted, in kW. Optional; supplying it says whether that size looks plausible against this estimate."
        },
        "nonHeatingFraction": {
          "type": "number",
          "description": "Share of that fuel used for something other than heating and hot water, such as a gas hob, as a decimal. A hob is usually 0.03 to 0.05. Defaults to 0."
        },
        "summerMonthFuelUse": {
          "type": "number",
          "description": "Fuel used in a single summer month, in the same unit, when the heating is off. Give this if it can be found: almost all of it is hot water, so it separates hot water from space heating exactly and removes the biggest assumption in the estimate."
        },
        "applianceEfficiency": {
          "type": "number",
          "description": "Seasonal efficiency of the existing boiler as a decimal. Defaults to a realistic figure for the fuel instead of the one on the badge."
        },
        "electricityPricePerKwh": {
          "type": "number",
          "description": "Price of a unit of electricity, in pounds. Optional."
        }
      },
      "additionalProperties": false
    }
    arguments 81 lines
  • connection_route unknown 1h ago

    Work out which ENA connection procedure a domestic installation of solar panels, batteries or both falls under: connect first and notify the distribution network operator within 28 days, or apply and wait for approval before anything is connected. The rules are the ENA's engineering recommendations, not MCS documents: EREC G98 for small installations, EREC G99 for everything larger, and EREC G100 for export limitation. Every test is in amps per phase at a nominal 230 V, and it applies to the premises as a whole, so list EVERY inverter that can export, existing ones included. A battery counts as generation even if it only ever charges from the panels. The figure that counts is each inverter's registered capacity: its AC rating, or a lower limit the manufacturer has fixed. It is NOT the panels' kWp. A 4.4 kWp array on a 3.68 kW inverter is a 3.68 kW installation. Where an inverter has been capped below its hardware rating, give the hardware rating as 'designCapacityKw', because G99 tests that separately. The routes are: G98 when the total is 16 A per phase or less (3.68 kW single phase, 11.04 kW three phase); G99 SGI-1, also connect and notify, when the total is within 16 A but an inverter built for up to 32 A has been capped; G99 SGI-2 and SGI-3, fast track applications answered within 10 working days, which allow larger totals held back by a type-tested export limiter; and the standard G99 application for anything else. An export limiter NEVER brings an installation under G98. IMPORTANT: this says which procedure applies, not what the operator will decide. Approval depends on the local network, which only the operator can assess. Say so whenever you report a result. Method from EREC G98 / G99. These calculators follow the published MCS methods, for understanding a system and checking a quotation. Anything that gets installed still needs a design and a site survey from a certified installer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "devices"
      ],
      "properties": {
        "phases": {
          "type": "integer",
          "description": "The supply: 1 for single phase, which is almost every British house, or 3 for three phase. Defaults to 1."
        },
        "devices": {
          "type": [
            "null",
            "array"
          ],
          "items": {
            "type": "object",
            "required": [
              "kind",
              "registeredCapacityKw"
            ],
            "properties": {
              "kind": {
                "type": "string",
                "description": "'solar' for a solar inverter, 'battery' for an AC-coupled battery inverter, 'hybrid' for one inverter serving both panels and battery, or 'other'. Required."
              },
              "label": {
                "type": "string",
                "description": "A name for this device, for the breakdown."
              },
              "phase": {
                "type": "string",
                "description": "On a three phase supply, which phase the device is connected to: 'L1', 'L2', 'L3', or 'all' for a three phase inverter, which is split evenly. Ignored on a single phase supply. Defaults to 'L1'."
              },
              "existing": {
                "type": "boolean",
                "description": "True for a device that is already installed. It still counts toward the total. Defaults to false."
              },
              "designCapacityKw": {
                "type": "number",
                "description": "What the inverter was built to deliver before any fixed limit, in kW AC: G99 calls this the intrinsic design capacity. Only differs from 'registeredCapacityKw' for an inverter capped below its hardware rating. Defaults to the registered capacity."
              },
              "registeredCapacityKw": {
                "type": "number",
                "description": "The most the device can export, in kW AC: the inverter's rated output, or a lower limit the manufacturer has fixed so the customer cannot change it. From the datasheet or the ENA type test register. Not the panels' kWp. Required."
              }
            },
            "additionalProperties": false
          },
          "description": "Every inverter at the premises that can export: solar, battery and hybrid, existing ones included. A battery counts even if it only charges from the panels. At least one is required."
        },
        "exportLimitKw": {
          "type": "number",
          "description": "The export limit a fully type-tested G100 scheme would hold the premises to, in kW per phase, where one is proposed. Optional. An export limit never brings an installation under G98, but it decides which G99 route applies."
        },
        "otherInstallationsNearby": {
          "type": "boolean",
          "description": "True when the same installer has fitted, or plans to fit, generation at other premises within 500 metres, or on the same street, within 28 days either side. That turns a G98 notification into an application. Defaults to false."
        }
      },
      "additionalProperties": false
    }
    arguments 62 lines
  • hot_water_cylinder unknown never probed

    Work out the daily hot water demand of a dwelling and the size of cylinder a heat pump needs, using the formula in MIS 3005-D 3.5.2 and the BS 6700 guidance reproduced in MGD 007. The demand is 45 litres a day for each of N, where N is the greater of the number of bedrooms plus one and the number of people actually living there. For a new build, where occupancy is unknown, the bedroom count is used. The cylinder does not have to hold a whole day's demand, because it reheats as it empties. What it must cover is the largest draw-off before the heat pump catches up, which is why a larger heat pump needs a smaller cylinder: reheat time is volume times temperature rise, divided by 14.3 times the kW. The result gives the BS 6700 minimum, a recommended size rounded to a volume cylinders are made in, and the reheat time. Note that cylinder volume is not the whole story: a heat pump cylinder needs a much larger coil than a boiler cylinder, because the water arrives cooler and there is less temperature difference to drive heat across the surface. Method from MIS 3005-D. These calculators follow the published MCS methods, for understanding a system and checking a quotation. Anything that gets installed still needs a design and a site survey from a certified installer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "bedrooms"
      ],
      "properties": {
        "bedrooms": {
          "type": "integer",
          "description": "Number of bedrooms in the property. Required."
        },
        "bathrooms": {
          "type": "integer",
          "description": "Number of bathrooms with a bath. Defaults to 1."
        },
        "occupants": {
          "type": "integer",
          "description": "Number of people who actually live there, if known. MIS 3005-D takes the greater of this and bedrooms plus one. Leave it out for a new build, where the occupancy is not yet known."
        },
        "storageTemp": {
          "type": "number",
          "description": "Temperature the cylinder is stored at, in Celsius. Defaults to 55, which is a common heat pump setting. A weekly pasteurisation cycle above 60 is separate."
        },
        "coldWaterTemp": {
          "type": "number",
          "description": "Incoming mains temperature in Celsius. Defaults to 10."
        },
        "heatPumpOutputKw": {
          "type": "number",
          "description": "Heat output of the heat pump in kW when it is heating the cylinder. A larger heat pump reheats faster, so it needs less stored volume. Defaults to 6."
        }
      },
      "additionalProperties": false
    }
    arguments 33 lines
  • radiator_flow_temperature unknown never probed

    Work out the flow temperature a heat pump must produce to heat a room through a given radiator, and the resulting MCS Heat Emitter Guide star rating, following section 4 of MGD 007. This is the calculation that decides whether a heat pump will be cheap or expensive to run. A heat pump's efficiency falls as the water temperature rises, by roughly two to three per cent per degree, and the temperature it must produce is set by the radiators, not by the machine. Supply the room's design heat loss in watts, from a room-by-room calculation, and the rated output of the radiator in that room. British catalogues normally quote at a mean-water-to-air difference of 50 K; if yours quotes 60, say so and the figure is restated. The result gives the oversize factor, which is the radiator's output at 50 K divided by the room's heat loss, and converts it to a required flow temperature through the BS EN 442 output law. Star ratings run from 0 to 6, one star per five degrees of flow temperature, with six stars at 35 degrees. Run this for every room. A house runs at the flow temperature its worst room demands, so one undersized radiator sets the running cost for the whole house. Method from MGD 007. These calculators follow the published MCS methods, for understanding a system and checking a quotation. Anything that gets installed still needs a design and a site survey from a certified installer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "roomHeatLossW",
        "radiatorOutputW"
      ],
      "properties": {
        "roomTemp": {
          "type": "number",
          "description": "Internal design temperature of the room in Celsius. Defaults to 21."
        },
        "systemDeltaT": {
          "type": "number",
          "description": "Designed drop in water temperature between flow and return, in kelvin. Heat pump systems commonly use 5; boiler systems used 10 or 20. Defaults to 5."
        },
        "ratedAtDeltaT": {
          "type": "number",
          "description": "The mean-water-to-air temperature difference the rated output was quoted at. British catalogues normally quote 50; some older ones quote 60. Defaults to 50."
        },
        "roomHeatLossW": {
          "type": "number",
          "description": "The room's design heat loss in watts, from a room-by-room heat loss calculation. Required."
        },
        "radiatorOutputW": {
          "type": "number",
          "description": "Rated output of the radiator or radiators in that room, in watts, at the catalogue temperature. Required."
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • room_heat_loss unknown never probed

    Calculate the design heat loss of a single room in watts, following BS EN 12831 as MIS 3005-D applies it. This is the figure a heat pump is sized from and the figure the radiator in that room must be able to deliver. BS EN 12831 is a room-by-room method. Run this once for each heated room and add the results; sizing a heat pump from floor area alone is what produces the oversized installations that cycle all winter. Internal design temperatures come from Table 1 of MIS 3005-D and follow from the room type: 22 for a bathroom, 21 for living and dining rooms, 18 for bedrooms, halls, kitchens and toilets. These are minimums, so a higher figure is accepted and a lower one is refused. External design temperatures come from Table 2, for eight locations, in two columns: 'a' is the 99% figure and 'b' the colder 99.6% one, which needs no uplift for intermittent heating. Each element needs an area, a U-value, and a kind. The kind matters because it fixes which temperature difference applies. Walls, windows, doors, roofs and suspended floors lose heat to the outside design temperature. A SOLID FLOOR ON THE GROUND loses heat to the local annual average air temperature instead, which is far warmer, and getting this wrong is the commonest error in a heat loss calculation. Window and door areas belong to the window and the door, not to the wall behind them. Method from MIS 3005-D. These calculators follow the published MCS methods, for understanding a system and checking a quotation. Anything that gets installed still needs a design and a site survey from a certified installer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "location",
        "floorAreaM2",
        "elements"
      ],
      "properties": {
        "elements": {
          "type": [
            "null",
            "array"
          ],
          "items": {
            "type": "object",
            "required": [
              "kind",
              "areaM2",
              "uValue"
            ],
            "properties": {
              "kind": {
                "type": "string",
                "description": "One of 'external_wall', 'window', 'door', 'roof', 'suspended_floor', 'ground_floor' or 'unheated_space'. Required."
              },
              "label": {
                "type": "string",
                "description": "A name for this element, so the result can be read back against the survey."
              },
              "areaM2": {
                "type": "number",
                "description": "Area of the element in square metres. Window and door areas are taken out of the wall area, not counted twice. Required."
              },
              "uValue": {
                "type": "number",
                "description": "U-value in W/m2K: the watts lost through each square metre for every degree of temperature difference. Required."
              },
              "unheatedTemp": {
                "type": "number",
                "description": "Temperature of the unheated space on the other side, in Celsius. Only used for the 'unheated_space' kind. Defaults to halfway between inside and outside."
              }
            },
            "additionalProperties": false
          },
          "description": "Every surface through which the room loses heat. At least one is required."
        },
        "location": {
          "type": "string",
          "description": "Which of the eight tabulated locations the property is nearest: 'belfast', 'birmingham', 'cardiff', 'edinburgh', 'glasgow', 'london', 'manchester' or 'plymouth'. Required."
        },
        "roomName": {
          "type": "string",
          "description": "A name for the room."
        },
        "roomType": {
          "type": "string",
          "description": "Which of the tabulated room types this is: 'living_room', 'dining_room', 'bedsitting_room', 'bathroom', 'bedroom', 'kitchen', 'hall' or 'toilet'. Sets the internal design temperature. Defaults to 'living_room'."
        },
        "designBasis": {
          "type": "string",
          "description": "'a' for the 99% outside design temperature or 'b' for the colder 99.6% figure. Column B needs no uplift for intermittent heating. Defaults to 'a'."
        },
        "floorAreaM2": {
          "type": "number",
          "description": "Floor area of the room in square metres. Required, and used with the ceiling height to work out the ventilation loss."
        },
        "internalTemp": {
          "type": "number",
          "description": "Internal design temperature in Celsius, if it should differ from the tabulated value for the room type. MIS 3005-D sets the tabulated values as a floor, not a target, so a higher figure is allowed and a lower one is not."
        },
        "ceilingHeightM": {
          "type": "number",
          "description": "Floor to ceiling height in metres. Defaults to 2.4."
        },
        "airChangesPerHour": {
          "type": "number",
          "description": "How many times an hour the air in the room is replaced. A draughty old room may be 1.5 or more; a well sealed new one 0.5. Defaults to 1."
        }
      },
      "additionalProperties": false
    }
    arguments 81 lines
  • solar_pv_output unknown never probed

    Estimate the annual AC electricity output of a UK solar photovoltaic system, in kWh, using the standard estimation method that MIS 3002 requires every MCS certified installer to use. The method is: annual output = kWp x Kk x SF, where Kk is read from the MCS irradiance dataset for the site's postcode zone, roof pitch and orientation, and SF is a shade factor between 0 and 1. Supply the postcode and the array's capacity in kWp, plus the roof's pitch in degrees from horizontal and its orientation in degrees away from due south in either direction, so that south is 0, south-east and south-west are both 45, east and west are both 90, and north is 180. The result carries the tabulated yield, the estimate, and what the same array would produce at the best pitch and orientation for that zone, so a roof that is merely good is not mistaken for a poor one. This covers the United Kingdom only; the dataset has no values for anywhere else. Method from MIS 3002. These calculators follow the published MCS methods, for understanding a system and checking a quotation. Anything that gets installed still needs a design and a site survey from a certified installer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "capacityKwp",
        "orientation",
        "inclination"
      ],
      "properties": {
        "zone": {
          "type": "string",
          "description": "MCS postcode zone code, for example '5E'. An alternative to 'postcode' when the zone is already known."
        },
        "postcode": {
          "type": "string",
          "description": "UK postcode of the installation, for example 'BS1 5TR'. Only the outward code matters. Give this or 'zone'."
        },
        "capacityKwp": {
          "type": "number",
          "description": "Total installed capacity in kilowatts peak: the sum of the nameplate watts of every module, divided by 1000. Required."
        },
        "inclination": {
          "type": "number",
          "description": "Pitch of the array in degrees from horizontal. A flat roof is 0 and a wall-mounted array is 90. Required."
        },
        "orientation": {
          "type": "number",
          "description": "Degrees the array faces away from due south, in either direction, so due south is 0, south-east and south-west are 45, east and west are 90, and due north is 180. Required."
        },
        "shadeFactor": {
          "type": "number",
          "description": "Proportion of output left after shading, between 0.5 and 1. Use 1 for a clear horizon. Defaults to 1."
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • solar_pv_self_consumption unknown never probed

    Estimate what proportion of a domestic solar PV system's annual output is consumed in the house and what proportion is exported, using the lookup tables in MGD 003. The tables are not a model. They come from half-hourly monitoring of real British households by Loughborough University, with battery behaviour modelled on top, so they carry the real shape of domestic demand: a peak before the sun is up, another after it has gone, and a quiet middle of the day. Three things index them. The annual generation, which comes from the MIS 3002 output estimate. The household's annual consumption from a bill based on actual meter readings, which defaults to the British average of 3,500 kWh where it is unknown. And the weekday occupancy pattern, which is 'home_all_day', 'in_half_the_day' or 'out_all_day'; where the pattern is unknown MGD 003 says to use the middle one, and that is what an omitted value resolves to. Battery capacity is the USABLE capacity, which is smaller than the figure printed on the battery. Supplying import and export prices adds a value in pounds to the result. Note that self-consumption is not the same as independence from the grid, and the result reports both. Method from MGD 003. These calculators follow the published MCS methods, for understanding a system and checking a quotation. Anything that gets installed still needs a design and a site survey from a certified installer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "annualGenerationKwh"
      ],
      "properties": {
        "occupancy": {
          "type": "string",
          "description": "Weekday occupancy pattern: 'home_all_day', 'in_half_the_day' or 'out_all_day'. Defaults to 'in_half_the_day', which is what MGD 003 says to use when the pattern is unknown."
        },
        "batteryKwh": {
          "type": "number",
          "description": "Usable capacity of any battery in kWh, which is smaller than the headline capacity. Omit or use 0 for no battery."
        },
        "exportPricePerKwh": {
          "type": "number",
          "description": "What the household is paid for a unit exported, in pounds. Optional."
        },
        "importPricePerKwh": {
          "type": "number",
          "description": "What the household pays for a unit of grid electricity, in pounds. Optional; supplying it adds a value to the result."
        },
        "annualGenerationKwh": {
          "type": "number",
          "description": "Expected annual AC output of the PV system in kWh, as produced by the MIS 3002 estimation method. Required."
        },
        "annualConsumptionKwh": {
          "type": "number",
          "description": "The household's annual electricity consumption in kWh, from a bill based on actual meter readings. Defaults to 3500, which MGD 003 uses where the figure is unknown."
        }
      },
      "additionalProperties": false
    }
    arguments 33 lines
  • solar_pv_shading unknown never probed

    Convert a completed MCS sunpath shading assessment into a shade factor, using the procedure in MGD 005. The MCS sunpath chart is divided into 84 segments, each worth one per cent of the year's useful irradiance. An assessor stands at the middle of where the array will go, plots what blocks the horizon onto the chart, and counts the segments covered. This tool takes that count and returns 1 minus the loss, which is the SF term in the MIS 3002 output estimate. Objects within ten metres of the array are near shading and are assessed separately, from each affected part of the array, not from its middle. They can be listed here for the record, but MGD 005 is explicit that near shading has a considerable effect and should be avoided. This tool does not perform the assessment. It does the arithmetic on an assessment somebody made. Method from MGD 005. These calculators follow the published MCS methods, for understanding a system and checking a quotation. Anything that gets installed still needs a design and a site survey from a certified installer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "segments"
      ],
      "properties": {
        "segments": {
          "type": "integer",
          "description": "Number of segments on the MCS sunpath chart that the obstruction touches, from 0 to 84. Each segment is worth one per cent of the year's irradiance."
        },
        "nearObjects": {
          "type": [
            "null",
            "array"
          ],
          "items": {
            "type": "object",
            "required": [
              "segments",
              "modulesAffected"
            ],
            "properties": {
              "segments": {
                "type": "integer",
                "description": "Segments the object touches on the sunpath chart, from 0 to 84."
              },
              "description": {
                "type": "string",
                "description": "What the object is, for example 'chimney' or 'television aerial'."
              },
              "modulesAffected": {
                "type": "integer",
                "description": "How many modules in the array this object shades."
              }
            },
            "additionalProperties": false
          },
          "description": "Objects within ten metres of the middle of the array, each assessed from its own position on the array. Optional."
        }
      },
      "additionalProperties": false
    }
    arguments 42 lines
  • solar_pv_system_size unknown never probed

    Work out the solar PV system a UK home needs: the capacity in kWp, the number of panels, the battery to go with it, and what it would do to the electricity bill. This runs the MCS arithmetic backwards. The other solar calculators here each answer one question about a system somebody has already specified. This one starts from what a household uses and arrives at the system that covers it, which is the question a householder actually has. The chain is short and every link is published. Annual consumption sets the generation the array has to make. The MCS irradiance dataset behind MIS 3002 says what one kWp makes on that roof, which gives a capacity. Capacity divided by panel size gives a panel count, rounded up, because panels come whole. The MGD 003 tables then say how much of that generation the household will use and how much it will export. Only the postcode and the roof direction are required. Direction is a compass point, not an angle: 'S', 'SE', 'SW', 'E', 'W', 'NE', 'NW' or 'N'. Give the annual consumption from a bill if it is known, since the 3,500 kWh default is only the British average. Shading can be described in words instead of measured, and a roof area caps the panel count where the roof is the constraint. No cost is assumed. Installed prices vary far too much between houses to guess at, so a payback figure appears only when a cost from a real quotation is supplied. Use this to size a system or to sanity-check a quotation. Use 'solar_pv_output' instead when the capacity is already known and the question is only what it will generate. Method from MIS 3002. These calculators follow the published MCS methods, for understanding a system and checking a quotation. Anything that gets installed still needs a design and a site survey from a certified installer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "postcode",
        "direction"
      ],
      "properties": {
        "shading": {
          "type": "string",
          "description": "How much shading the roof has, in words: 'none', 'light', 'moderate' or 'heavy'. Defaults to 'none'. Use 'shadeFactor' instead if a proper MGD 005 assessment has been done."
        },
        "postcode": {
          "type": "string",
          "description": "UK postcode of the property, for example 'BS1 5TR'. Only the outward code matters. Required."
        },
        "direction": {
          "type": "string",
          "description": "Compass point the roof faces: 'S', 'SE', 'SW', 'E', 'W', 'NE', 'NW' or 'N'. Required."
        },
        "occupancy": {
          "type": "string",
          "description": "Weekday occupancy: 'home_all_day', 'in_half_the_day' or 'out_all_day'. Decides how much of the generation is used at home instead of exported. Defaults to 'in_half_the_day'."
        },
        "panelWatts": {
          "type": "number",
          "description": "Nameplate rating of a single panel in watts. Defaults to 440, which is typical of a current domestic module."
        },
        "roofAreaM2": {
          "type": "number",
          "description": "Shade-free roof area available for panels, in square metres. Optional; when given it caps the number of panels."
        },
        "inclination": {
          "type": "number",
          "description": "Roof pitch in degrees from horizontal. Defaults to 35, which is typical of a British pitched roof. A flat roof is 0."
        },
        "shadeFactor": {
          "type": "number",
          "description": "A measured shade factor between 0.5 and 1 from an MGD 005 assessment. Overrides 'shading' when given."
        },
        "installedCost": {
          "type": "number",
          "description": "The installed cost of the system in pounds, from a quotation. Optional; supplying it gives a payback period. No cost is assumed if it is left out, because prices vary too much to guess at."
        },
        "includeBattery": {
          "type": "boolean",
          "description": "Whether to size a battery alongside the panels. Defaults to false."
        },
        "batteryModuleKwh": {
          "type": "number",
          "description": "Nominal capacity of one battery module in kWh. Batteries are sold in whole modules, so the answer rounds up to one. Defaults to 5."
        },
        "exportPricePerKwh": {
          "type": "number",
          "description": "What the household is paid for a unit exported, in pounds. Optional."
        },
        "annualConsumptionKwh": {
          "type": "number",
          "description": "The household's electricity use in kWh a year, from a bill. Defaults to 3500, which is the British average and the figure MGD 003 falls back on, but a real bill sharpens the answer considerably."
        },
        "electricityPricePerKwh": {
          "type": "number",
          "description": "What the household pays for a unit, in pounds. Optional; supplying it puts a value on the answer."
        }
      },
      "additionalProperties": false
    }
    arguments 66 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1060b1593f467ebe.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1060b1593f467ebe/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1060b1593f467ebe/badge.svg)](https://brick.blue/agent/1060b1593f467ebe?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.