Skip to main content
Glama

List GSA destinations

get_destinations
Read-onlyIdempotent

Returns the paginated list of every GSA destination rate area with its numeric ID, display name, defined scope, county and state, ordered by ID (offset, limit; past the end is an empty list). Use the ID with get_gsa_perdiem_by_destination or calculate_trip_per_diem. No rates; a ZIP or state lookup is usually faster than browsing.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of destinations to return. The maximum is 200.
offsetNoNumber of destination records to skip before returning results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds ordering ('ordered by ID'), the past-the-end semantics ('an empty list'), and the scope exclusion ('No rates'). It stops short of stating a default page size or rough dataset size, which would fully inform a browsing decision.

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 sentences, front-loaded with what is returned, then how to use the ID, then the efficiency caveat. Every clause carries information; nothing is repeated from the schema or annotations.

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 correctly takes on the burden of listing returned fields and pagination shape, and it closes the loop by naming the tools that consume the returned IDs. Nothing an agent needs to call this 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 earns a bump by adding behavioral meaning the schema lacks — that offset/limit paginate an ID-ordered list and that an out-of-range offset yields an empty list rather than an error.

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 paginated list of every GSA destination rate area') and enumerates the returned fields (numeric ID, display name, scope, county, state), which lets an agent distinguish it from get_destination_by_id and the state/ZIP-based per-diem lookups without opening a 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 explicit downstream usage ('Use the ID with get_gsa_perdiem_by_destination or calculate_trip_per_diem') and an explicit when-not ('No rates; a ZIP or state lookup is usually faster than browsing'), naming the faster alternative categories by their sibling tools.

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