Skip to main content
Glama

Superpass

Get where the chip is

get_chip_location
Read-onlyIdempotent

Use this when the person asks where the chip is in a passport or ID card, or why their iPhone does not read it. Give the country as a two-letter code or its English name. Not for whether a document is genuine: only the Superpass app reads and checks a chip. Answers where the chip is in that country's passport and how to hold an iPhone to read it, the older design if one is still valid, whether its ID card has a chip an iPhone reads and what opens it, the source the answer comes from and how sure it is, and the page on superpass.me.

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": {
      "country": "<country>"
    },
    "name": "get_chip_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesa two-letter code (de) or the English name (Germany)

Output Schema

NameRequiredDescriptionDefault
countryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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. Beyond that the description adds real context: the answer includes the chip location, iPhone holding instructions, an older design caveat, ID-card coverage, the source and confidence of the answer, and a superpass.me page. It stops short of noting country-coverage limits or what happens for an unsupported country.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The trigger is front-loaded and the exclusion is placed early, so an agent gets the decision-relevant content first. The final sentence is a long run-on list of answer contents that could be tightened, but every clause carries information rather than filler.

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

Completeness4/5

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

With one required param, full schema coverage, annotations and an output schema, the description does the remaining work well by explaining scope, exclusion and answer content. The one gap is country coverage — it never says whether all countries are supported or what the result is for an unknown country, which matters given the list_countries sibling.

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 parameter description already says 'a two-letter code (de) or the English name (Germany)'. The description restates that same fact rather than adding format, casing, or normalization rules, so it neither helps nor hurts beyond the schema baseline.

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 concrete triggering intent ('where the chip is in a passport or ID card, or why their iPhone does not read it') and names the exact resource and scope. It also bounds the tool ('Not for whether a document is genuine'), so an agent can separate it from list_countries and send_feedback without opening any schema.

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?

It states both when to use it (user asks where the chip is, or why their iPhone fails to read it) and when not to (document genuineness, which only the Superpass app checks). That is explicit positive and negative guidance plus a redirect, which is the top of the scale.

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