Skip to main content
Glama

Get a visa bulletin

get_visa_bulletin
Read-onlyIdempotent

A visa bulletin's employment and family charts (final action dates and dates for filing), as the State Department printed them. The newest by default. Example: {"month":"2026-10"}.

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

Input Schema

NameRequiredDescriptionDefault
monthNoThe bulletin's month, back to 2005-06. Leave out for the newest. Example: 2026-10.

Output Schema

NameRequiredDescriptionDefault
asOfYesThe date the data is true for, YYYY-MM-DD, when one applies.
dataYesThe answer, or found: false when no record matched.
pageYesThe page on permtracker.app that shows the same thing. Cite it.
sourceYesWho published the underlying records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower — and the description still adds real value with "as the State Department printed them," telling the agent this is raw published data with no normalization or editorializing. It also discloses the default resolution (newest). It does not mention pagination or update cadence, but the output schema covers return shape.

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?

Two tight sentences plus a compact example — the payload definition comes first and the default behavior second, which is the right order. The inline example largely duplicates the example already present in the schema, a small redundancy, but nothing is padded.

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 one-optional-parameter read tool with full schema coverage, an output schema, and complete annotations, the description supplies what an agent needs to call it correctly. Minor residual gap: it doesn't say whether non-employment/family charts (e.g., diversity visa) are included or excluded, so the agent must open the output schema to confirm scope.

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 the single parameter already carries its own description, range hint (back to 2005-06), and example. The description mainly restates the default rather than adding new meaning about the month format or boundaries. Baseline 3 is appropriate.

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 names a specific resource (visa bulletin) and enumerates the exact payload — employment and family charts, final action dates and dates for filing. That is far more precise than the bare name. It stops short of a verb-led statement and never differentiates itself from the surrounding lookup tools, but the content scope is unambiguous.

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?

The only usage signal is the default behavior ("The newest by default"), reinforced by the schema note to omit the month for the latest bulletin. There is no statement of when an agent would want a historical bulletin versus the current one, and no exclusions or alternatives are mentioned. Adequate but purely implied beyond the default case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.