Skip to main content
Glama

Fox River Press

Compare home Level 2 chargers

compare_chargers
Read-onlyIdempotent

Home Level 2 EV chargers side by side, every maker value read from the maker's own page on a stated day. Give a breaker size to see what each would draw on that circuit, and a connector to keep only chargers for that port. No prices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "compare_chargers"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectorNoThe car's charge port
breaker_ampsNoThe circuit's breaker, for example 40, 50 or 60

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive behavior, so the description's job is to add context — and it does: values are read from the manufacturers' own pages on a stated day (freshness/provenance) and pricing is deliberately excluded (a hard scope limit). It does not say how many chargers come back or how missing data is handled, but it adds real value beyond the annotations.

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

Conciseness5/5

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

Two sentences, both front-loaded with the most decision-relevant facts: the resource and comparison mode first, then the two optional filters, then the scope exclusion. The 'No prices' fragment is terse but earns its place as a boundary marker.

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

Completeness4/5

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

For a zero-required-param, closed-world read tool with an output schema absent, this covers purpose, provenance, both filters, and a key exclusion. What is missing is any hint of result shape — which spec fields are compared, or whether coverage varies by maker — which an agent would want since no output schema exists.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: supplying breaker_amps changes the displayed draw per charger, and connector acts as a filter restricting results to that port. That is a semantic effect, not a restatement of 'The circuit's breaker' or 'The car's charge port'.

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?

Names a specific verb and resource ('Home Level 2 EV chargers side by side') plus a provenance claim ('every maker value read from the maker's own page on a stated day'), so the agent knows this is a spec comparison, not an install-cost estimate. It does not name the closest sibling (home_charging_estimate), though 'No prices' implicitly draws the boundary.

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?

The description tells the agent what each optional input does and why to supply it ('Give a breaker size to see what each would draw', 'a connector to keep only chargers for that port'), which implies both params are optional filters. It never states when to choose this tool over home_charging_estimate or when it is the wrong tool, so routing guidance is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources