Skip to main content
Glama

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

Plug types and voltage of a country

country_plugs
Read-onlyIdempotent

Which plug types, voltage and frequency does a country use (by ISO code or name)? More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": {
      "code": "<code>"
    },
    "name": "country_plugs"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesISO code or country name.

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, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only the returned data fields (plug types, voltage, frequency) and then spends a sentence on an unrelated promo link, contributing little behavioral context such as lookup failure behavior for invalid country names.

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 front-loaded and efficient, stating purpose in one clause. The second sentence is pure promotional content for an unrelated API catalog and does not help an agent select or 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?

For a simple one-parameter lookup, the description tells the agent what information comes back, which compensates for the missing output schema. However, it omits error behavior for unrecognized country names and gives no differentiation from the many similar plug-related 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 coverage is 100% for the single 'code' parameter, so the baseline is 3. The description's '(by ISO code or name)' restates the schema's own 'ISO code or country name' description without adding format, casing, or validation details.

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 a specific resource (plug types, voltage, frequency for a country) with a clear input mechanism (ISO code or name), so the agent knows exactly what it returns. It does not distinguish itself from close siblings such as plug_types, plug_countries, or search_plug_countries, which appear to overlap in scope.

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 explicit when-to-use or when-not-to-use guidance, and no reference to any alternative tool. The parenthetical '(by ISO code or name)' is the only hint about invocation context, so the agent must infer routing among several plug-related siblings on its own.

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