Skip to main content
Glama

DTMO CONUS locations by state

get_dtmo_conus_locations
Read-onlyIdempotent

Returns the DTMO per diem locations of a US state (US-XX code) with location name and county, as named in the Department of Defense CONUS table. Use it to find the name for the q filter of get_dtmo_perdiem_conus. Returns no rates. For other countries, Alaska, Hawaii and territories use get_dtmo_oconus_locations.

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_conus_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
state_isoYesUS state code: US- followed by the postal abbreviation, e.g. US-CA for California.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 job is supplementary. It adds meaningful behavior context: the data source (DoD CONUS table), that no rates are returned, and the shape of each result (name + county). It stops short of describing list size, ordering, or whether an empty result is possible for a valid state code.

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 short sentences, front-loaded with the primary purpose, followed by the usage hook and the exclusion/alternative. Every sentence carries distinct information and none is wasted on restating the title.

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?

For a single-parameter read-only lookup with full schema coverage and rich annotations, the description covers purpose, routing, and the returned fields. The only remaining gap is return-cardinality detail (whether the response is a flat list and how large a state's location set can be), which matters slightly more because there is no output schema.

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 the state_iso format is fully documented in the schema itself. The description restates the "US-XX code" convention without adding new syntax, constraints, or failure behavior beyond what the schema already says. Baseline 3 applies when the schema does the heavy lifting.

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 the DTMO per diem locations of a US state") and names the exact fields returned (location name and county) from the DoD CONUS table. It also explicitly delimits scope by saying "Returns no rates" and pointing OCONUS/Alaska/Hawaii/territories queries to a named sibling, so an agent can distinguish it from get_dtmo_perdiem_conus 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 Guidelines5/5

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

Gives a concrete use case — resolving the location name to feed the `q` filter of get_dtmo_perdiem_conus — which is an explicit when-to-use rule. It also names the exclusion set (other countries, Alaska, Hawaii, territories) and the alternative tool to use instead, leaving nothing to inference.

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