Skip to main content
Glama

GSA per diem rates by ZIP code and date

get_gsa_perdiem_by_zipcode
Read-onlyIdempotent

Returns the GSA per diem for a US ZIP code (five digits or ZIP+4) in effect today or on date: seasonal lodging and daily M&IE in USD. 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_year for a whole fiscal year.

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>"
    },
    "name": "get_gsa_perdiem_by_zipcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoThe day the rates must be in force, YYYY-MM-DD; today when omitted. 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 / date / description
      Previous value: -"Specific date in YYYY-MM-DD format"New value: +"The day the rates must be in force, YYYY-MM-DD; today when omitted. 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 per diem 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.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description correctly spends its words on behavior annotations cannot express: one ZIP may resolve to multiple destinations and all rates are returned with county and none is auto-selected, and a ZIP with no non-standard destination falls back to the Standard CONUS rate. These are exactly the edge-case outcomes an agent needs to interpret the response.

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 tight sentences, front-loaded with verb, resource and scope, then ambiguity behavior, then fallback, then the sibling routing hint. Every sentence carries a distinct decision-relevant fact with no repetition or filler.

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?

With no output schema, the description does the necessary work of describing what comes back (lodging and M&IE amounts, per-destination county, CONUS fallback), which is enough to interpret results. It leaves the verification_url output behavior entirely to the schema and says nothing about response shape or how many destinations is typical, a minor residual gap for a lookup 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 coverage is 100%, so both the ZIP format rules and the date plan-limit constraints are already fully documented in the schema. The description restates the ZIP formats (five digits or ZIP+4) and the default-to-today behavior without adding syntax or semantics beyond the schema, and it never mentions verification_url. 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 verb and resource ("Returns the GSA per diem for a US ZIP code") plus the exact outputs (seasonal lodging and daily M&IE in USD) and the effective-date scope. It also distinguishes itself from the nearest sibling by naming get_gsa_perdiem_by_zipcode_year, so an agent can route without opening a 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 a clear selection rule against one alternative ("Use get_gsa_perdiem_by_zipcode_year for a whole fiscal year") and implicitly positions itself as the single-date/single-ZIP lookup. It does not explicitly address the other lookup siblings (by_destination, by_state, search_perdiem), so the routing 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