Skip to main content
Glama

GSA trip per diem calculator

calculate_trip_per_diem
Read-onlyIdempotent

Estimates GSA CONUS per diem for a multi-stop trip: a day-by-day breakdown and totals of payable lodging and M&IE. Each stop has inclusive arrival and departure dates and a GSA destination ID or ZIP code, optionally the actual nightly lodging cost and meals to deduct. Applies the rate in effect each day, 75% M&IE on first and last days, the official meal deductions and the lodging cap (excess reported as overage). Not for Department of Defense or foreign travel.

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": {
      "stops": "<stops>"
    },
    "name": "calculate_trip_per_diem"
  }
}

Input Schema

NameRequiredDescriptionDefault
stopsYesOrdered, contiguous TDY-locality stops for the trip.
deductible_mealsNoSparse caller-determined meal deductions, keyed by trip date.
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. Changed2 schema fields changed
    • changedInput schema / properties / verification_url / default
      Previous value: -falseNew value: +true
    • changedInput schema / properties / verification_url / description
      Previous value: -"Include deduplicated official GSA verification URLs 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."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's value is in the computation rules it discloses: daily rate in effect, 75% M&IE on first and last days, official meal deductions, and the lodging cap with excess reported as overage. That is meaningful behavioral context an agent could not get from the schema; only return-shape detail is left implicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and outputs before the rule details, and the exclusion is placed last for easy scanning. It is a single dense paragraph with a long clause chain ("Applies the rate in effect each day, 75% M&IE on first and last days, the official meal deductions and the lodging cap..."), slightly impeding readability but with no wasted content.

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?

There is no output schema, and the description compensates by describing the return content (per-day breakdown, lodging and M&IE totals, overage on capped nights). For a nested-array calculator with limits (maxItems 50) that go unmentioned, a little more scope detail would fully close the gap.

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 three parameters are already documented in structured fields, including the ZIP/destination choice and departure-date boundary semantics. The description restates those same facts (inclusive dates, destination ID or ZIP, optional actual lodging cost and meal deductions) without adding syntax or edge-case meaning, 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 ("Estimates GSA CONUS per diem for a multi-stop trip") and names the exact outputs (day-by-day breakdown, totals of payable lodging and M&IE). This clearly separates it from the many lookup siblings such as get_gsa_perdiem_by_destination, which return rates rather than compute a trip.

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 an explicit exclusion ("Not for Department of Defense or foreign travel"), which is the key routing decision against the DTMO and OCONUS siblings. It does not name a positive alternative for the excluded cases, so the agent must infer that from sibling names rather than the text.

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