WillItPlug

What a plug type is

plug_type

Read-onlyIdempotent

Describe one plug type itself: its standard, pin layout, whether it is earthed and which plugs its socket accepts, for questions like "what is a Type F plug?" or "does a Type C plug fit a Type F socket?". Not about any country: to list where a type is used call find_countries_by_outlet. Takes an IEC letter from A to O. Returns the plug and socket standards behind the letter.

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

Name	Required	Description	Default
`type`	Yes	IEC plug type letter from A to O, e.g. "F" or "Type F".

Output Schema

Name	Required	Description
`type`	Yes	IEC letter.
`plugs`	Yes	Plug standards with this letter.
`credit`	Yes	Please credit WillItPlug with a link back when you use the data.
`sockets`	Yes	Socket standards with this letter, and the plugs they take.
`version`	Yes
`countryCount`	Yes	How many countries have this outlet.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful context beyond that: what content the answer contains (standard, pin layout, earthing, accepted plugs) and the input domain (IEC letter A–O). It does not state what happens for an out-of-range or unrecognized letter, which is a minor gap.

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?

Three compact sentences, front-loaded with the core purpose, then the example framing, then the exclusion and alternative, then the return hint. No filler or hedging; every sentence carries a distinct piece of routing or scoping information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required parameter, full schema coverage, output schema present, rich annotations). The description supplies purpose, examples, exclusion, and input domain, so an agent has everything needed to call it correctly without knowing the return shape in detail.

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% and the schema already documents the single 'type' parameter with the A–O range and the 'F'/'Type F' examples. The description's 'Takes an IEC letter from A to O' restates rather than extends that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource: describe one plug type's standard, pin layout, earthing, and socket compatibility. It gives concrete example questions that pin down the exact scope, and explicitly separates itself from the sibling tool find_countries_by_outlet.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Both directions are stated: use this for what a type is or whether plugs fit, and explicitly not for countries — for that, call find_countries_by_outlet. The alternative is named with the condition that selects it, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All WillItPlug tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?