Skip to main content
Glama

GSA per diem rates by state and fiscal year

get_gsa_perdiem_by_state_year
Read-onlyIdempotent

Return every GSA destination rate in a US state (US-XX) for a US fiscal year (October 1 to September 30): the lodging rate for every month and the daily M&IE rate per destination. The optional location filters destinations by GSA destination or defined-area name, case-insensitive and partial. Set verification_url=true to include the official GSA state lookup URL. Use get_gsa_perdiem_by_state 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": {
      "state_iso": "<state_iso>",
      "year": "<year>"
    },
    "name": "get_gsa_perdiem_by_state_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.
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 / 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 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 readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description adds the meaningful behavioral detail that a fiscal year runs October 1 to September 30 and that results span every month of lodging plus a daily M&IE figure. It does not mention the sandbox/Pro/Business date-window limits, though those live in the schema.

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 sentences, each earning its place: what is returned, how `location` narrows it, what the verification flag does, and the alternative tool. The scope statement is front-loaded before the optional-parameter detail.

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 spelling out the shape of the response (per-month lodging rates and a daily M&IE rate per destination). Combined with full schema coverage of the four parameters, nothing an agent needs to call this correctly 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%, so all four parameters are already documented, and the description largely restates them (case-insensitive partial `location`, `verification_url=true` including the GSA link). The only genuine addition beyond the schema is the explicit October 1–September 30 fiscal-year framing, which is also present in the `year` field description.

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?

The description opens with a specific verb and resource ("Return every GSA destination rate") and pins the scope to a state (US-XX) and a defined federal fiscal year. It also names the sibling it is not (get_gsa_perdiem_by_state), so an agent can distinguish the two 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?

It gives an explicit routing rule: use get_gsa_perdiem_by_state for a single date's rate, implying this tool for the full-year sweep. That covers the closest sibling, but it says nothing about when to prefer get_gsa_perdiem_by_zipcode_year or get_gsa_perdiem_by_destination, which are also plausible competitors.

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