Skip to main content
Glama

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

Do I need a plug adapter or converter?

travel_adapter_check
Read-onlyIdempotent

Traveling from one country to another: do my plugs fit, do I need an adapter, and do I need a voltage converter for my device? 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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "travel_adapter_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination: ISO code or name.
fromYesHome country: ISO code or name.
plugsNoYour plug types instead of the home country's (e.g. "C" for a Europlug charger).
deviceNoThe input voltage on your device's label: 230 or 100-240.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/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 and the description carries a lighter burden. It does add value by indicating the three things the answer covers (fit, adapter, converter), which is the only clue to return content since there is no output schema. It says nothing about accuracy caveats, multiple plug types per country, or how partial answers are handled.

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?

The single question sentence is front-loaded and free of waste. The input was scored against the full definition, and no redundant restatement of the name or schema is present in the descriptive text.

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 two-required-parameter lookup with no output schema, the description tells the agent what questions get answered but not what form the answer takes (e.g., list of plug types, voltage comparison, yes/no flags). The optional plugs and device parameters are explained only in the schema. It is adequate but leaves the agent guessing about the response shape.

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%, with all four parameters documented inline, including examples for plugs ("C") and device ("230 or 100-240"). The description adds no parameter-level meaning of its own, 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 a concrete task with a concrete resource: checking whether plugs fit, whether an adapter is needed, and whether a voltage converter is needed when traveling between two countries. It is phrased as a user question rather than a statement of what the tool returns, and it never distinguishes itself from related plug/voltage lookups, 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 Guidelines3/5

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

The scenario ("Traveling from one country to another") implies when to reach for it, which is the only usage signal present. There is no explicit when-not guidance, no mention of prerequisites, and no indication of how it differs from a simpler country-plug lookup.

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