Skip to main content
Glama
Sign In

SurePassportPhoto

by io.github.githubatlas
OverviewDiscussionsAdmin

Get the link to make the photo on surepassportphoto.com

get_make_link
Read-onlyIdempotent

A link that opens the photo tool for one document, so the user takes or uploads the photo on their own device. The photo is processed privately in the user's browser and is never sent through this connection: never ask the user for the photo here. Returns JSON text with 'url' (give it to the user), an 'instruction' sentence and an 'attribution' line.

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_make_link"
  }
}

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.
clientNoShort lower-case name of the assistant for the link's utm_medium, e.g. 'claude', 'gemini', 'chatgpt'. Default 'assistant'.
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?

The annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the photo is processed privately in the user's browser and never transits this connection, and it enumerates the returned JSON fields (url, instruction, attribution) despite there being no output schema. Only auth/rate-limit context is absent.

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?

Three tight sentences, each carrying a distinct fact (what the link is, the privacy constraint, the return shape). It opens with a noun phrase rather than the action, which slightly delays the point, but there is no 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?

For a three-parameter, non-destructive read tool with full schema coverage, the description covers what the agent must do (pass a slug from find_document, hand the URL to the user) and what comes back. The only gap is the lack of any sibling comparison, which matters given get_photo_spec sits next to it.

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 each parameter (slug, client, locale) is documented in the schema with format, pattern and enum. The description adds no meaning beyond that — it never mentions the client attribution parameter or locale selection for the linked page, so baseline 3 applies.

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 concrete outcome — a link that opens the photo tool for one document — rather than restating the tool name. It is clear what the agent gets back, but it never names or contrasts itself with get_photo_spec, which is the most plausible confusable sibling.

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?

Guidance is implied rather than stated: the slug is 'exactly as returned by find_document', which signals a prerequisite call, and 'give it to the user' plus 'never ask the user for the photo here' define the handoff. There is no explicit statement of when to prefer this over get_photo_spec, nor any exclusion beyond the photo-collection warning.

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