Skip to main content
Glama

Search DSSR per diem by name

search_perdiem
Read-onlyIdempotent

Finds DSSR per diem by a partial, case-insensitive country or post name of at least three characters, with no country code needed. Returns lodging, M&IE and maximum per diem per matching post, today or on date, with the post code for precise follow-up lookups. A name that matches nothing is a 404 error, not an empty list. Once the ISO code is known, the country tools are more precise.

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": {
      "q": "<q>"
    },
    "name": "search_perdiem"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesRequired case-insensitive substring of a location or country name; at least three characters after trimming.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description still adds real behavioral value: the fields returned per matching post (lodging, M&IE, maximum, post code), the today-vs-date default, and the 404-on-no-match behavior instead of an empty list.

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 sentences, front-loaded with the core matching rule and ending with the routing hint, with no filler. There is minor redundancy with the schema on the three-character and case-insensitivity points, but the density is otherwise justified.

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 covers the return payload, the error case, the date default and the handoff path to more precise code-based tools. Nothing an agent needs in order to call this correctly and interpret the result is missing.

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%, and the schema already spells out the case-insensitive substring rule, the three-character minimum after trimming, the YYYY-MM-DD format, the today default and per-plan date limits. The description restates the matching and date semantics more compactly and adds only 'no country code needed' beyond the schema, so 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 ('Finds DSSR per diem') plus the exact matching semantics (partial, case-insensitive, minimum three characters, no country code required). It also distinguishes itself from the code-based siblings by noting that country tools are more precise once the ISO code is known.

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 an explicit when-to-use condition (you only have a name fragment) and an explicit alternative ('Once the ISO code is known, the country tools are more precise'). It also documents the failure mode, a 404 rather than an empty list, which shapes how an agent should handle a miss.

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