Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

Every country's plugs and voltage

plug_countries
Read-onlyIdempotent

Plug types, voltage and frequency for every country (compact), optionally filtered. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": "plug_countries"
  }
}

Input Schema

NameRequiredDescriptionDefault
plugNoPlug type A-O.
voltageNoVolts, within 10 V.
frequencyNo50 or 60.
confidenceNohigh, medium or low.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered without the description. The description adds only the '(compact)' note about result size, and says nothing about response shape, pagination, or how the filter combination behaves when multiple optional filters are supplied.

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

Conciseness3/5

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

The first sentence is tight, front-loaded and useful. The second sentence is a promotional link ('More APIs from FitzTopPicks...') with UTM tracking that consumes roughly half the description without helping an agent invoke the tool.

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?

With no output schema, the description does at least enumerate the returned fields (plug types, voltage, frequency), which covers the essentials for zero required parameters. However, given several near-identical plug-related siblings, it leaves the agent unable to judge how this 'compact' variant differs in result size or filter behavior.

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 plug, voltage, frequency and confidence are all already documented (including the 10 V tolerance and the 50/60 enum values). The description contributes nothing beyond 'optionally filtered', so the baseline 3 applies.

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?

The description names the concrete resource and payload: plug types, voltage and frequency for every country, with an optional filter. That is specific enough for an agent to know what comes back, but it never distinguishes itself from the closely-named siblings (country_plugs, search_plug_countries, plug_type), so the '(compact)' tag is the only hint at a difference and it is unexplained.

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?

'Optionally filtered' describes a capability rather than telling the agent when to choose this tool over country_plugs or search_plug_countries. There is no when-to-use, when-not-to-use, or alternative routing guidance anywhere in the text.

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