Skip to main content
Glama
Sign In

SurePassportPhoto

by io.github.githubatlas
OverviewDiscussionsAdmin

Get the official photo rules for a document

get_photo_spec
Read-onlyIdempotent

The official photo requirements of one document: print size in mm and inches, pixel size, digital file limits, head height and eye line as percentages of the photo height, background, glasses, expression, head covering, photo age, the authority's own guidance on photos taken at home, the source URL and the date it was last verified. Returns JSON text; numbers are millimetres, pixels, kilobytes or percentages as named. Quote the 'url' and the 'attribution' line in the answer and offer 'makeUrl' when the user wants the photo made.

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": {
      "slug": "<slug>"
    },
    "name": "get_photo_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesDocument slug in the form '<country-slug>/<document-slug>', exactly as returned by find_document (for example 'united-states/passport', 'india/passport', 'schengen/schengen-visa'). The ISO-code form 'us/passport' is also accepted.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With readOnlyHint/idempotentHint already covering the safety profile, the description adds real value: it discloses the return format (JSON text), the unit conventions (mm, pixels, KB, percentages 'as named'), the presence of a source URL and a last-verified date. It does not say what happens for an unknown slug, which keeps it short of a 5.

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 purpose and field inventory are front-loaded, and the closing sentences give actionable follow-up steps. The field enumeration is long but each item is informative, so wording is dense rather than wasteful.

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?

There is no output schema, so the description must carry return-value context, and it does by listing the fields and stating the JSON text format and unit semantics. Only error/not-found behavior and the meaning of the referenced 'makeUrl' are left unaddressed.

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 description coverage is 100%, and both slug format and the locale enum are fully documented in the schema, including the note that official quotes and numbers are language-invariant. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies; its unit note concerns output rather than inputs.

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?

The description states a specific resource (official photo requirements of one document) and enumerates the exact fields returned, so an agent knows precisely what it gets. It does not explicitly distinguish itself from siblings like find_document or get_make_link, relying instead on the schema's reference to find_document for slug provenance.

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 guidance is present but focused on what to do after the call (quote 'url' and 'attribution', offer 'makeUrl') rather than on when to choose this tool over alternatives. The dependency on find_document is implied only through the slug parameter description, not stated in the tool description itself.

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