Skip to main content
Glama

City Pair airport and city codes

get_city_pair_locations
Read-onlyIdempotent

Returns the airport or metropolitan codes GSA uses in City Pair airfare awards for the fiscal year of date (today by default), with city, state and country. GSA decides whether a city uses airport codes (DCA, IAD) or a metro code (WAS), so resolve codes here before get_city_pairs. q (3+ characters) matches a code exactly or a city or country name by substring. Fiscal years other than the current one depend on the plan.

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

Input Schema

NameRequiredDescriptionDefault
qNoMatch a code exactly or a city/country name by substring; case-insensitive. Omit to list every code of the fiscal year.
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.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world behavior, so the safety profile is covered. The description adds real context beyond that: the fiscal year is derived from `date` (today by default), code granularity is GSA's choice rather than the caller's, and older fiscal years are plan-dependent. It does not describe result shape beyond the listed fields, which is a minor gap for a tool with no output schema.

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?

Three dense sentences, front-loaded with the purpose and then the sibling relationship, with no filler. The closing line 'Fiscal years other than the current one depend on the plan' is slightly cryptic on its own, since the actual plan limits live in the schema rather than here.

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?

For a two-parameter, optional-parameter lookup tool, the description covers purpose, ordering relative to the downstream sibling, matching semantics, and the fiscal-year default. Nothing an agent needs to call it correctly is missing, and the plan-limit detail is properly delegated to the schema.

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, but the description adds the derivation relationship the schema does not state — that `date` selects the fiscal year of the award rather than merely 'the day rates must be in force'. It also restates the `q` matching rule and 3+ character minimum, which is largely redundant with the schema.

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 airport/metro codes GSA uses in City Pair awards) plus the fields returned (city, state, country). It explicitly separates itself from the sibling get_city_pairs by positioning this as the code-resolution step that precedes it.

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 ordering rule: 'resolve codes here before get_city_pairs', and explains why (GSA decides whether a city uses airport codes like DCA/IAD or a metro code like WAS). It also flags the fiscal-year caveat for non-current years, so the agent knows the scope boundary.

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