Skip to main content
Glama

lookup_zip_perdiem

Read-only

Look up federal per diem rates by ZIP code.

Accepts 5-digit ZIPs or ZIP+4 (e.g., '02101' or '02101-1234'). Bundled fiscal years are answered from GSA's published ZIP file with no API call; other years use the GSA Per Diem API.

GSA sets rates by county or locality, and about 1,800 ZIPs span more than one rate area. The result's status is 'resolved' when every rate area GSA lists for the ZIP has the same rate, otherwise 'ambiguous' with all candidates and no single rate chosen. county (optional) selects the candidate for that county.

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": {
      "zip_code": "<zip_code>"
    },
    "name": "lookup_zip_perdiem"
  }
}

Input Schema

NameRequiredDescriptionDefault
countyNo
zip_codeYes
fiscal_yearNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/non-destructive; the description adds material behavior on top — a local-file fast path versus a network call, and a 'resolved' vs 'ambiguous' outcome contract with the fact that ~1,800 ZIPs map to multiple rate areas. That is exactly the kind of non-obvious runtime behavior an agent needs before calling.

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?

Front-loaded with purpose, then input formats, then data-source behavior, then result semantics — a logical escalation with no filler. The parenthetical examples and the '1,800 ZIPs' figure each earn their space by justifying the ambiguity contract.

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?

An output schema exists, so return values need not be re-explained, yet the description still defines the status field's meaning and how county resolves ambiguity — covering the hardest part of the tool. The only real gap is fiscal_year's accepted values and default, which an agent would need to call it confidently.

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 coverage is 0%, so the description carries the burden: it fully documents zip_code's accepted formats (5-digit and ZIP+4 with examples) and explains county's role in disambiguating candidates. fiscal_year is only alluded to via 'bundled fiscal years' versus 'other years' — no default, valid range, or what omitting it means — leaving one of three parameters under-specified.

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?

Opens with a specific verb and resource ('Look up federal per diem rates by ZIP code') and immediately scopes itself to ZIP-keyed lookup, which separates it from lookup_city_perdiem and lookup_state_rates. An agent can choose among the three lookup siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real conditional guidance: bundled fiscal years are served locally with no API call, other years hit the GSA API, and county should be supplied when the ZIP spans multiple rate areas. It stops short of explicitly contrasting itself with the sibling lookup tools, so it is clear context rather than full when/when-not routing.

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.