Skip to main content
Glama
Sign In

SurePassportPhoto

by io.github.githubatlas
OverviewDiscussionsAdmin

Find a passport, visa or ID photo document

find_document
Read-onlyIdempotent

Resolve a user's country and document into the slug the other tools take. Pass the words the user used ('India passport', 'Schengen visa', 'UK passport digital', '2x2'). Returns JSON text with up to 5 matches, each with 'slug' (use it for get_photo_spec and get_make_link), the country, the document family, the title and a 'url' to cite, plus an 'attribution' line to quote with the answer.

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": {
      "query": "<query>"
    },
    "name": "find_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe user's words for the document, usually country plus document type, e.g. 'Canada passport' or 'US visa'.
localeNoLanguage of the prose fields (title, summary, rules). One of: en, es, fr, de, pt, hi, ar, zh, ru, vi, tr, id, ja. Default 'en'. Official quotes and every number are identical in all languages.
countryNoOptional country name, alias, ISO code or slug to restrict the matches to one country, e.g. 'India', 'UK', 'us'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 safety is covered. The description adds behavior the annotations cannot: a cap of up to 5 matches, the returned field set, a 'url' to cite and an 'attribution' line to quote. The one gap is no stated behavior for no-match or multi-match results, which is material for a resolver.

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 sentences, front-loaded with the core action, then input examples, then the return contract. No restatement of the title or name, and every clause carries information the agent needs.

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 no output schema, the description correctly carries the return shape, field names, match limit and citation expectations, which is the right burden for a lookup tool. It omits disambiguation and empty-result handling, the main remaining unknown for a resolver.

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 description coverage is 100%, so the baseline is 3. The description still adds meaning beyond the schema by showing that 'query' accepts loose user phrasing including bare size tokens like '2x2', and by tying the returned 'slug' to specific downstream parameters.

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: 'Resolve a user's country and document into the slug the other tools take.' It also positions the tool in the chain by naming get_photo_spec and get_make_link as consumers of the slug, so an agent can place it relative to siblings 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 Guidelines4/5

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

Gives concrete input guidance ('Pass the words the user used') with varied examples spanning country+document and size-only queries, which tells the agent when this tool applies. It does not state exclusions or what to do on zero/ambiguous matches, so it stops short of full when/when-not guidance.

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

All SurePassportPhoto toolsInspect
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