Passport, visa and ID photo sizes, head size and background rules from official sources.
Scored across 2 tools
The two tools are clearly distinct: list_photo_specs returns a collection with filters, while get_photo_spec retrieves full details for a single spec by id. There is no overlap in purpose and the descriptions make the boundary obvious.
Both tools follow a consistent verb_noun pattern in snake_case (get_photo_spec, list_photo_specs). The naming is predictable and easy to parse.
Only two tools are provided. While this may be sufficient for a narrow read-only lookup service, it falls below the typical 3–15 range and feels thin; additional operations (e.g., filtering by document type or searching) could justify more tools.
The list and get pair covers the core lookup workflow for ID photo specs, including country filtering and detailed retrieval. Minor gaps exist, such as filtering by document type or searching by spec name, but these are workable by listing all specs first.
One ID photo spec: print size in mm, head size and how it is measured, allowed backgrounds and whether the background may be changed, online pixel size and file limit where there is one, who takes the photo, the official source and the date it was checked, and a link to make the photo in the browser. Always pass on the notes; they say what the photo must not be used for.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Spec id from list_photo_specs. | |
| locale | No | Language of the linked page. Default en. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by listing what the response contains and emphasizing that notes must always be passed on because they state prohibited uses.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the resource and its contents, and every clause maps to useful return-value information or an important output-handling instruction. It is compact for a tool with no output schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description effectively explains the return contents in detail, including size, background rules, source, check date, browser link, and notes. Combined with full parameter coverage and read-only annotations, it gives an agent enough to invoke and use the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and both the id and locale parameters are already documented in the schema. The description does not add meaning beyond the schema for either parameter, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource as a single ID photo spec and enumerates the specific contents returned, making it distinguishable from the sibling list_photo_specs. An agent can tell this is the detail-fetch operation for one spec.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by the single-spec-by-id nature and by the schema note that the id comes from list_photo_specs. However, the description does not explicitly state when to call this instead of the list tool or mention any prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
The passport, visa, ID card and other ID photo specs fotosize has checked against official sources, with an id for get_photo_spec. Filter by country code. can_make_here is false where the photo must be taken at the office or fotosize does not make it.
| Name | Required | Description | Default |
|---|---|---|---|
| country | No | Country code: us (United States), uk (United Kingdom), es (Spain), mx (Mexico), br (Brazil), jp (Japan), de (Germany), nl (Netherlands), tr (Turkey), vn (Vietnam), id (Indonesia), in (India), lat (Latin America), kr (South Korea). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare a safe read-only, closed-world operation. The description adds useful behavioral context beyond annotations: specs are checked against official sources and can_make_here false has a specific operational meaning.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loads the resource, then adds filtering and can_make_here semantics. It is slightly awkwardly phrased but contains little wasted text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter list tool with a fully described enum and no output schema, the description covers the resource, the filter, the id handoff to get_photo_spec, and can_make_here semantics. It does not state what happens when country is omitted, but the definition is otherwise sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, including a fully documented country enum. The description only repeats that results can be filtered by country code and adds no syntax or default behavior beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource as ID photo specs checked against official sources and explains that each spec has an id for get_photo_spec. This distinguishes it from the sibling detail tool and tells an agent exactly what the tool provides.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says to filter by country code and implies the list-to-detail workflow by mentioning the id for get_photo_spec. It lacks an explicit when-not-to-use statement, but the sibling relationship is clear enough for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
get_photo_speclist_photo_specsPassport and visa photo rules for 110 documents in 60 countries, and upload limits as exact numbers.
Turn a portrait into a compliant passport, visa or ID photo. 300+ official specs, 3 free a day.
Passport visa, entry & transit requirements for any country pair, with official government sources.
Visa & entry requirements for 199 passports, cited to official sources and re-verified daily.
Add one secure layer between your agents and this server.
