Skip to main content
Glama

GSA per diem rates by state and date

get_gsa_perdiem_by_state
Read-onlyIdempotent

Returns every GSA destination rate in a US state (US-XX) in effect today or on date: seasonal lodging and daily M&IE in USD per destination, with its county. location filters by destination or defined-area name, case-insensitive and partial. A state with no non-standard destination returns the Standard CONUS rate. CONUS only: for Alaska, Hawaii, territories and abroad use the DTMO or DSSR tools.

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": {
      "state_iso": "<state_iso>"
    },
    "name": "get_gsa_perdiem_by_state"
  }
}

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.
locationNoOptional case-insensitive partial match against the GSA destination name or location-defined name.
state_isoYesTwo-letter US postal abbreviation for the state or District of Columbia.
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 state 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.3/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 safety profile is covered. The description adds genuine behavior beyond that: the Standard CONUS fallback when a state has no non-standard destination, and that the government verification link is returned by default. It does not discuss result volume or ordering, which is a minor gap.

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?

Three tight sentences: the return payload and date default lead, the location filter follows, and the scope exclusion closes. No filler, and the most decision-relevant constraint (CONUS only) is placed where an agent will see it.

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, yet the description discloses the payload shape (lodging and M&IE per destination, with county), currency, the default-today date semantics, and the empty-result fallback. Combined with a fully documented schema, an agent has everything needed to call this correctly.

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 each parameter is already documented, including plan-based date limits and the verification_url default. The description restates the state code format and the case-insensitive partial matching of `location` without adding syntax or semantics the schema lacks, so the 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 every GSA destination rate in a US state on a given date, including seasonal lodging, daily M&IE in USD, and county. It also scopes itself against siblings by declaring CONUS-only coverage and directing OCONUS lookups to the DTMO/DSSR tools, so an agent can distinguish it from get_gsa_perdiem_by_zipcode, by_destination, and by_state_year.

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 explicit when-not guidance with named alternatives: Alaska, Hawaii, territories and abroad should use the DTMO or DSSR tools. It does not explicitly say when to prefer this over the zipcode- or destination-scoped GSA variants, leaving the state-vs-zipcode routing to inference from the names.

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