Skip to main content
Glama

Search DTMO per diem by name

search_dtmo_perdiem
Read-onlyIdempotent

Finds Department of Defense per diem by location name ('Kabul') or country or state name ('Afghanistan'), across CONUS and OCONUS, with no code needed. Returns lodging, local and proportional meal rates, incidentals and maximum per diem per matching location and season. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_dtmo_perdiem"
  }
}

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.
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

A3.9/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 added value is the disclosure of returned rate components and the season/fiscal-year default. Remaining gaps are minor: it does not say what happens when the query matches many locations or no location, and plan-based date restrictions live only in the schema rather than the prose.

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?

The purpose and scope are front-loaded in the first sentence, with the return payload and date semantics following in order of importance. 'with no code needed' is the only phrase that reads as promotional filler rather than operational 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?

With no output schema, the description carries the return-value burden and does so by enumerating the rate components per matching location and season. For a zero-required-parameter read tool whose four inputs are fully documented in the schema, nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description rises above it by explaining the date-vs-year tradeoff, the Oct 1–Sep 30 fiscal year definition, and the omit-both default, and by giving concrete query examples ('Kabul', 'Afghanistan'). It says nothing about verification_url, though the schema documents that parameter thoroughly.

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 gives a specific verb and resource ('Finds Department of Defense per diem') plus the lookup key (location, country or state name) and scope ('across CONUS and OCONUS'), and it lists what comes back (lodging, meals, incidentals, max per diem). That implicitly separates it from the CONUS-only and OCONUS-only siblings, but the near-identical 'search_perdiem' sibling is never addressed explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage guidance is limited to the date/year selector ('omit both for the current fiscal year'), which is parameter behavior rather than tool selection. There is no statement about when to prefer this over get_gsa_perdiem_by_zipcode, get_dtmo_perdiem_conus, or search_perdiem, and no note on whether date and year may be combined.

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