Skip to main content
Glama

DTMO CONUS per diem by state

get_dtmo_perdiem_conus
Read-onlyIdempotent

Department of Defense per diem for the continental U.S. by state code (e.g. 'TX'); Alaska, Hawaii and the territories are served by the OCONUS endpoint. Returns lodging, local and proportional meal rates, incidentals and the maximum per diem (lodging + meals + incidentals) per season. q filters by location name. date selects the rates in force on that day, year a fiscal year (Oct 1 to Sep 30); omit both for the current 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": {
      "state_iso": "<state_iso>"
    },
    "name": "get_dtmo_perdiem_conus"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch by location name or state/country name
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.
yearNoA fiscal year starts Oct 1st, ends Sep 30th. 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.
limitNo
offsetNo
state_isoYesUS state code: US- followed by the postal abbreviation, e.g. US-CA for California.
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 / 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."
    • changedInput schema / properties / year / description
      Previous value: -"A fiscal year starts Oct 1st, ends Sep 30th"New value: +"A fiscal year starts Oct 1st, ends Sep 30th. 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: -"If 'True', will include a verification url in the payload, pointing to the official government source. This is useful to crosscheck that the API returns the proper data and for auditing."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.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world behavior, so the description's job is narrower and it delivers: it discloses the return payload (lodging, local and proportional meal rates, incidentals, maximum per diem) and that rates are returned per season. It does not mention pagination or how many records a state query yields.

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?

Four tight sentences, front-loaded with the resource and coverage scope before the parameter notes. No filler, though the state-code example is a wasteful inaccuracy rather than a helpful clarification.

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 enumerating the returned rate components and noting the per-season granularity. Pagination via `limit`/`offset` and the multiple-records-per-state behavior are left unexplained, which is a modest gap for a 7-parameter list-style tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Actually a 3: with 71% schema coverage the schema already documents `q`, `date`, `year`, `state_iso` and `verification_url` in detail. The description restates `q`, `date` and `year` and adds only the useful combined rule that omitting both date and year yields the current fiscal year; `limit` and `offset` are untouched, and the 'TX' example conflicts with the schema's US-XX format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb+resource (DoD per diem for the continental U.S., keyed by state code) and explicitly carves out Alaska, Hawaii and the territories as the OCONUS endpoint's job, which separates it from get_dtmo_perdiem_oconus. One flaw: it illustrates the key as 'TX' while the schema requires 'US-TX', so an agent could pass the wrong format. It also does not distinguish itself from the GSA per-diem siblings.

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 clear routing rules: use the OCONUS endpoint for AK/HI/territories, use `q` to filter by location name, and omit both `date` and `year` to get the current fiscal year. What is missing is guidance on when to prefer this over get_gsa_perdiem_by_state or search_dtmo_perdiem, which are the closest alternatives in the sibling list.

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