Skip to main content
Glama
Sign In

SmartTools

by io.github.9thShini
OverviewDiscussionsAdmin

Electricity cost calculator

electricity_cost_calculator

Running cost of an appliance per day, month and year from its wattage. Runs on smart-tools.xyz.

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": {
      "power_watts": "<power_watts>",
      "hours_per_day": "<hours_per_day>",
      "price_per_kwh": "<price_per_kwh>"
    },
    "name": "electricity_cost_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage for the source_url link (default en)
power_wattsYesPower draw in watts
hours_per_dayYesHours used per day
price_per_kwhYesElectricity price per kWh

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It states the output provides costs 'per day, month and year', but does not mention whether the operation is read-only, how results are returned, or any side effects. The platform note adds no behavioral context.

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?

The description is concise and front-loaded, with the core purpose in the first sentence. The second sentence about running on smart-tools.xyz is low-value but not verbose, so the overall structure remains efficient.

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?

For a simple calculator with no output schema, the description explains that output is per day, month, and year, which is helpful. However, it does not mention the locale parameter or any details about result formatting, so it is not fully complete.

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 the schema already documents each parameter. The description adds only 'from its wattage', which reiterates the power_watts parameter. No additional meaning is provided beyond the schema, so the baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool's function: 'Running cost of an appliance per day, month and year from its wattage.' This specifies the verb (calculate running cost), the resource (appliance cost from wattage), and distinguishes it from siblings like fuel_cost_calculator or energy_converter.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives, such as when to choose electricity_cost_calculator over energy_converter or fuel_cost_calculator. It only mentions that it 'Runs on smart-tools.xyz', which is not usage guidance.

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

All SmartTools toolsInspect
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