Skip to main content
Glama
Sign In

orizn-visa-mcp

by io.github.MattJeff
OverviewDiscussionsAdmin

Recent visa rule changes

get_recent_changes
Read-onlyIdempotent

Recently changed visa rules — what changed, for which passport/destination pair, on what date, and from which official source. STATUS: Orizn's change feed is currently OFF and this tool returns {status:"unavailable", changes: []}. It was shut down because it was publishing internal data edits as if they were official policy changes. An empty answer here therefore means "Orizn has no verified change data", NEVER "nothing changed" — do not tell the user rules are stable, tell them to check the destination's official immigration source, and use check_visa_requirement for the current rule with its verification date. Keyless, costs nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_recent_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of changes to return (1-200, default 50).
sinceNoOptional ISO date (YYYY-MM-DD) — only changes detected on or after this date.
passportNoOptional ISO 3166-1 alpha-3 passport code to filter on (e.g. 'FRA').
destinationNoOptional ISO 3166-1 alpha-3 destination code to filter on (e.g. 'JPN').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses critical behavior beyond the annotations: the feed is shut down, returns {status:'unavailable', changes: []}, and was shut down because it published internal edits as official policy changes. It also explains the semantic trap that an empty answer means no verified data, not that nothing changed.

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?

The description is front-loaded with the tool's intended purpose before immediately flagging the unavailable status. Every sentence adds necessary context: return shape, shutdown reason, empty-result interpretation, alternative tool, and cost.

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

Completeness5/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 supplies the actual return shape and explains the unavailable status. It also covers the key interpretive risk of empty results and points to the correct sibling tool, making it complete for an agent deciding how to use or avoid this tool.

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%, so the schema already documents limit, since, passport, and destination in detail. The description mentions passport/destination filtering and dates conceptually but does not add syntax or format details beyond the schema, so the baseline 3 is appropriate.

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 states a specific resource and scope: recently changed visa rules, including what changed, passport/destination pair, date, and source. It also distinguishes the tool from check_visa_requirement by explaining that this is a change feed while check_visa_requirement reports the current rule with its verification date.

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 explicitly says the change feed is OFF and returns an unavailable status, so an empty result must never be interpreted as rules being stable. It directs the agent to tell users to check the destination's official immigration source and to use check_visa_requirement for the current rule.

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

All orizn-visa-mcp 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