Skip to main content
Glama

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

Find countries by plug type or voltage

search_plug_countries
Read-onlyIdempotent

Find countries by name or by plug type (e.g. "type G"), voltage or frequency. 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": "search_plug_countries"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoName, code, alias or "type X".
plugNoPlug type A-O.
limitNo1-100 (default 20).
voltageNoVolts (90-260), matched within 10 V.
frequencyNo50 or 60.
confidenceNohigh, medium or low.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that: no note on result ordering, matching behavior, or what an empty result means. Its one extra sentence is marketing with UTM tracking, not 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.

Conciseness3/5

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

The first sentence is well front-loaded and compact, listing the searchable facets immediately. The second sentence is a promotional link with campaign parameters that consumes roughly half the description's length without helping an agent invoke the tool. Removing it would make this a tight one-liner.

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?

With no output schema, the description's job is to convey what the tool searches over, and it does name the four search dimensions, while annotations and a fully documented six-parameter schema cover the rest. All parameters are optional, which the agent can see from the schema. The main omission is disambiguation from the many overlapping plug and country siblings.

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 every one of the six parameters is already documented with type, bounds and meaning, including the 10 V matching tolerance and the 50/60 frequency enum. The description's mention of name, "type G", voltage and frequency merely restates what the schema says. Baseline 3 applies since the schema carries the load.

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 ("Find") and resource ("countries") and enumerates the searchable dimensions: name, plug type, voltage, frequency. That is clear enough for an agent to know what the tool returns conceptually. It does not distinguish itself from plausible siblings like plug_countries, country_plugs or list_countries, so it stops short of a 5.

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?

There is no when-to-use or when-not-to-use guidance, and no named alternative for overlapping needs such as listing all countries or looking up a single country's plugs. The agent must infer from the description alone which of the several plug/country siblings to call. The only directional content is the second sentence, which is unrelated promotion.

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