WillItPlug

Countries with an outlet type

find_countries_by_outlet

Read-onlyIdempotent

Search for every country whose wall outlets are of one plug type, for questions like "which countries use Type G?" or "where else does my Type C plug work?". Use when the question starts from a plug type rather than a place; for one known country use country_plugs. Takes an IEC letter from A to O. Returns the matching countries with their voltage, frequency and page urls.

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": "find_countries_by_outlet"
  }
}

Input Schema

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

Output Schema

Name	Required	Description
`credit`	Yes	Please credit WillItPlug with a link back when you use the data.
`version`	Yes
`countries`	Yes	Countries with that outlet, sorted by name.
`outletType`	Yes	IEC letter that was asked for.

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, so the safety profile is covered. The description adds the exhaustive-set behavior ('every country', 'the matching countries') and the shape of the result (voltage, frequency, page urls), which tells the agent this is a complete enumeration rather than a sample.

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 short sentences ordered purpose, usage/alternative, input, then return. The capability statement is front-loaded and no sentence is filler, even with the alternative-routing clause packed in.

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?

A single-parameter lookup with annotations and an output schema needs little more, and the description still covers what it does, when to choose it, the accepted input range and the returned fields. Nothing an agent needs to call it correctly is missing.

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 itself documents the IEC plug letter with examples 'G' or 'Type G'. The description's 'Takes an IEC letter from A to O' largely restates that range, adding no format or normalization detail beyond it, 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?

States a specific verb and resource with clear scope: 'Search for every country whose wall outlets are of one plug type'. The example questions ('which countries use Type G?') make the reverse-lookup direction unambiguous, and naming country_plugs sharpens the distinction from the sibling.

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?

Explicit routing rule: 'Use when the question starts from a plug type rather than a place; for one known country use country_plugs.' That gives both the when and the when-not with a named alternative, leaving nothing for the agent to infer.

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?