Skip to main content
Glama

DTMO OCONUS locations by country

get_dtmo_oconus_locations
Read-onlyIdempotent

Returns the DTMO per diem locations of a country by ISO alpha-2 code ('AU', 'BE'), as named in the Department of Defense OCONUS table. location filters by case-insensitive substring, taken literally (no wildcards); no match returns an empty list. Use the names for the q filter of get_dtmo_perdiem_oconus. Returns no rates.

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": {
      "country_iso_code": "<country_iso_code>"
    },
    "name": "get_dtmo_oconus_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationNoFilter by location name
country_iso_codeYesISO 3166-1 alpha-2 country code, e.g. PG for Papua New Guinea; ZZ stands for 'Other Foreign Localities', not a country. Resolve a country name to its code with get_countries (q=name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, closed-world profile, so the description's job is to add behavior, and it does: literal case-insensitive substring matching, no wildcard interpretation, and an empty list on no match. It does not describe ordering of the returned locations, which is the only real gap.

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?

Roughly four short clauses, front-loaded with the return value, then the filter semantics, then the follow-up tool. Every sentence carries information; the backtick-quoted identifiers are slightly noisy but aid scanning.

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?

With only two parameters and no output schema, the description needs to imply the return shape, and "no match returns an empty list" plus "Returns no rates" does that adequately. Combined with the annotation safety profile and full schema coverage, an agent has what it needs to call this correctly.

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 a 3 is the baseline, but the description genuinely adds semantics the schema lacks: `location` is a literal, case-insensitive substring filter with no wildcard expansion. It also reinforces the ISO alpha-2 format for `country_iso_code` with concrete examples that match the schema's own examples.

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?

"Returns the DTMO per diem locations of a country by ISO alpha-2 code" gives a specific verb (returns), a specific resource (DTMO OCONUS locations), and a keyed access path. "Returns no rates" immediately separates it from the sibling get_dtmo_perdiem_oconus, and the OCONUS scoping distinguishes it from get_dtmo_conus_locations.

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 explicitly states the downstream use ("Use the names for the `q` filter of get_dtmo_perdiem_oconus") and implicitly excludes rate lookups by warning "Returns no rates." It never states a when-not condition in so many words, but the routing is clear enough to act on.

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