Skip to main content
Glama

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

One plug type

plug_type
Read-onlyIdempotent

What is a plug type (A to O)? Its description, the countries that use it and which sockets it fits. 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": {
      "type": "<type>"
    },
    "name": "plug_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesPlug type A-O.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 a closed-world scope, so safety is covered. The description adds what the response contains (description, countries, sockets), which is useful, but nothing about error behavior for invalid letters or output formatting.

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 substantive content is one compact sentence that is front-loaded correctly. The trailing promotional sentence about other APIs at fitztoppicks.com is pure noise for an agent and dilutes an otherwise tight definition.

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 carry the burden of describing return fields, and it lists them. However, for a tool whose whole purpose is returning structured facts about a plug type, more detail on the shape of those results (e.g., country names vs codes, socket list format) would help.

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% with a single parameter documented as 'Plug type A-O', so the baseline is 3. The description's parenthetical '(A to O)' reinforces the accepted value range, adding modest confirmation beyond the schema, though it doesn't specify single-letter case or format rules.

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 the resource (a single plug type), the valid range (A to O), and the three data points returned: description, countries using it, and compatible sockets. This distinguishes it reasonably from list-style siblings like plug_types and plug_countries, though the verb is expressed as a question rather than an action.

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?

Usage is only implied: an agent can infer this is the lookup for one specific plug type, but the description never states when to pick it over plug_types, country_plugs, or search_plug_countries. No prerequisites or exclusions are given.

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