Skip to main content
Glama

Latest data publications

get_latest_publications
Read-onlyIdempotent

Returns the most recent data loaded for each source, with its publication date and fiscal year: DSSR allowances and per diem, DTMO CONUS and OCONUS per diem, GSA per diem, mileage, vehicle rates and M&IE breakdowns, FEMA hotels and OPM pay tables. Use it to say how current an answer is. Returns no rates.

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": "get_latest_publications"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description goes beyond that by disclosing the payload's scope (publication date and fiscal year per source), the full list of sources covered, and an explicit exclusion (no rates) — genuinely useful behavior an agent cannot infer from annotations. It stops short of describing cardinality or ordering beyond "most recent per source".

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?

Front-loaded with what is returned, followed by a compact source enumeration that serves tool selection, then two short disambiguating sentences. The source list is long, but each item maps to a real sibling domain, so it earns its place; slight tightening would still help.

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 zero parameters but no output schema, the description must carry the return-value burden, and it largely does by naming the two returned fields (publication date, fiscal year) and the source dimension. What is missing is the response shape (e.g., list vs. object, one entry per source) — a minor but real gap for a metadata tool.

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?

The tool takes no parameters, so there is nothing to disambiguate; baseline 4 applies. The description correctly does not waste space on parameter talk and instead spends it on output scope.

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 most recent data loaded per source) and enumerates exactly which datasets are covered: DSSR allowances, DTMO CONUS/OCONUS per diem, GSA per diem, mileage, vehicle rates, M&IE, FEMA hotels, OPM pay tables. The closing "Returns no rates" cleanly separates it from the many sibling get_*perdiem/mileage tools.

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?

"Use it to say how current an answer is" gives an explicit trigger for calling this tool, which is the freshness/metadata role no sibling fills. It does not explicitly name alternatives or state when not to call it, but "Returns no rates" implicitly excludes all the rate-lookup siblings, so the routing is clear in practice.

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