Skip to main content
Glama

GSA per diem rates by ZIP code and fiscal year

get_gsa_perdiem_by_zipcode_year
Read-onlyIdempotent

Returns the GSA lodging rate for every month of a US fiscal year (October 1 to September 30) and the daily M&IE, in USD, for a US ZIP code (five digits or ZIP+4). A ZIP can map to several destinations; then every rate is returned with its county and none is chosen for you. A ZIP with no non-standard destination returns the Standard CONUS rate. Use get_gsa_perdiem_by_zipcode for the rate on one date.

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": {
      "zipcode": "<zipcode>",
      "year": "<year>"
    },
    "name": "get_gsa_perdiem_by_zipcode_year"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesFour-digit US fiscal year. Fiscal year 2026 runs from 2025-10-01 through 2026-09-30. Plan limits: Sandbox and Google add-on accounts may query dates within 30 days of today, Pro the current and previous US fiscal year, Business any date.
zipcodeYesFive-digit US ZIP code, or ZIP+4. ZIP+4 values are normalized to the first five digits.
verification_urlNoIncluded by default: a link to the official government table for the returned location and date, for the user to confirm the figures. Pass false to omit it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / year / description
      Previous value: -"Four-digit US fiscal year. Fiscal year 2026 runs from 2025-10-01 through 2026-09-30."New value: +"Four-digit US fiscal year. Fiscal year 2026 runs from 2025-10-01 through 2026-09-30. Plan limits: Sandbox and Google add-on accounts may query dates within 30 days of today, Pro the current and previous US fiscal year, Business any date."
  2. Changed2 schema fields changed
    • changedInput schema / properties / verification_url / default
      Previous value: -falseNew value: +true
    • changedInput schema / properties / verification_url / description
      Previous value: -"Include the official GSA ZIP-code lookup URL in the response when true."New value: +"Included by default: a link to the official government table for the returned location and date, for the user to confirm the figures. Pass false to omit it."
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent read; the description adds genuinely new behavior: a ZIP may map to multiple destinations and all rates are returned with county rather than one being chosen, and a ZIP with no non-standard destination falls back to the Standard CONUS rate. The fiscal-year boundary and USD currency are also called out, which matters for interpreting results.

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?

Four short sentences, front-loaded with what is returned, followed by the multi-destination caveat and the sibling routing. No filler or redundancy; each sentence carries a distinct fact.

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?

There is no output schema, and the description compensates by describing the shape of the return (monthly lodging rates, daily M&IE, county attribution, Standard CONUS fallback). Plan limits and the verification_url toggle are already fully covered by the schema, so nothing material is missing.

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 schema already defines the fiscal-year window, four-digit year, ZIP/ZIP+4 normalization, and verification_url default. The description restates the fiscal-year span and ZIP+4 tolerance but adds no new constraint or format detail, so baseline 3 applies.

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?

States a specific resource and scope: GSA lodging rate for every month of a US fiscal year plus daily M&IE in USD for a ZIP code. It also distinguishes itself from the single-date sibling by name, so an agent can pick between them without opening either 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?

Explicitly routes one-date lookups to get_gsa_perdiem_by_zipcode, which is the closest alternative and the most likely confusion point. It does not address the other near-neighbours (get_gsa_perdiem_by_state_year, get_gsa_perdiem_by_destination), so selection guidance is clear but not exhaustive.

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.

Resources