Skip to main content
Glama

Country State City

by io.github.pipeworx-io

Get Cities

get_cities
Read-onlyIdempotent

Get cities for a country, optionally filtered by state. Pass country_code (e.g., "US") and optionally state_code (e.g., "CA") to narrow results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyYesCountryStateCity API key
state_codeNoState/province code to filter by (e.g., "CA", "NY", "TX")
country_codeYesISO2 country code (e.g., "US", "IN")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesTotal number of cities returned
citiesYes
state_codeYesState code filter if provided, null if not
country_codeYesISO2 country code provided

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, covering safety and idempotency. The description adds filtering behavior and examples but doesn't address rate limits, authentication details, or response format beyond what annotations provide.

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?

Two sentences with no wasted words. The first sentence states the purpose and filtering capability; the second provides parameter examples. Front-loaded and efficient.

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 simple read-only lookup tool with full schema coverage, annotations, and an output schema, the description is complete. It covers all necessary context: what the tool returns, required parameters, optional filters, and usage examples.

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% with descriptions for all three parameters. The description adds concrete examples (e.g., 'US', 'CA') that are not in the schema, providing practical usage context beyond the bare parameter names.

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?

The description clearly states the tool retrieves cities for a country with optional state filtering, using specific verbs and resource types. It distinguishes itself from sibling tools like 'get_states' and 'list_countries'.

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?

The description specifies required (country_code) and optional (state_code) parameters with examples (e.g., 'US', 'CA'). While it doesn't explicitly state when not to use or direct to alternatives, the context from sibling tools provides implicit guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Country State City toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Several tools overlap enough to cause misselection: ask_pipeworx and ask_pipeworx_beta are functionally identical right now, ask_pipeworx_grounded and validate_claim both handle factual lookup/verification, and ai_visibility_check/scan_competitor_ai_presence are near duplicates in scope. The country/state/city tools are distinct but sit in a pile of unrelated Pipeworx tools, adding confusion.

Naming Consistency3/5

All names are lower_snake_case and families like polymarket_* and ask_pipeworx* help group tools, but the verb_noun convention is inconsistent: entity_profile, deep_research, recent_alerts, and pipeworx_trending are noun phrases, while remember/forget/subscribe are bare verbs. It is readable but not a predictable pattern.

Tool Count2/5

34 tools is above the practical ceiling for a focused MCP server, and the mismatch is severe: only 3 tools match the 'Country State City' name while 31 belong to a broad Pipeworx platform. A geographic server would need roughly 3-6 focused tools; this surface is bloted.

Completeness2/5

For the stated Country State City domain, list_countries/get_states/get_cities provide the basic hierarchy, but there is no city search, country/state detail lookup, or attribute discovery beyond the three list endpoints, making the useful geographic surface thin. For the Pipeworx domain the coverage is broader, but that confirms the identity mismatch and obscures the server's actual purpose.

Resources