a 1000 watts

Appliance running cost

appliance_running_cost

Read-onlyIdempotent

Estimate what an electrical appliance costs to run, from its wattage and hours of use, at a1000watts regional tariffs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "watts": "<watts>"
    },
    "name": "appliance_running_cost"
  }
}

Input Schema

Name	Required	Description	Default
`hours`	No	Hours of use to price.
`watts`	Yes	Rated power in watts, e.g. 1000.
`region`	No	gb, ni, iom or roi.	gb

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

B3.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The word 'Estimate' adds a useful hint that results are approximate, but the description says nothing about currency, tariff assumptions, or precision beyond that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that gets to the point with no filler, though the garbled 'a1000watts' segment hurts readability slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should explain what comes back (a cost figure, and in which currency). It omits the return value and the regional tariff assumption, leaving a real gap for a calculation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all three parameters (watts, hours, region enum) are already documented in the schema. The description only restates wattage and hours and never mentions the region parameter, adding no meaning beyond the schema — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Estimate') and resource ('what an electrical appliance costs to run') with the inputs that drive the calculation. It is distinguishable from the list-oriented siblings, though the mangled phrase 'at a1000watts regional tariffs' slightly obscures the tariff dimension.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the description — compute a running cost from wattage and hours — but there is no explicit when-to-use or when-not-to-use guidance, and no mention of the siblings list_energy_rates or list_ev_chargers as alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All a 1000 watts tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?