Skip to main content
Glama

cityparity — Cost-of-Living & Quality-of-Life Comparison

by com.cityparity

List supported cities by country

list_cities
Read-onlyIdempotent

List all city slugs supported by cityparity, grouped by country. Call this first to discover valid slugs before any other tool; the optional country filter narrows to one country. Read-only, no side effects; returns a text summary plus structured JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoOptional case-insensitive country filter. Use the canonical name as stored in city_data.country (e.g. "Norway", "USA", "United Kingdom"). If omitted, returns all countries.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
groupsYes
country_countYes

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already provide readOnlyHint and destructiveHint. Description adds 'no side effects' and 'returns a text summary plus structured JSON', which adds value beyond annotations.

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 concise sentences with front-loaded purpose and efficient additional guidance. No unnecessary words.

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?

Given low complexity, complete annotations, and existing output schema, the description covers purpose, usage order, safety, and return type sufficiently.

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 has 100% coverage with informative description for the country parameter. Description echoes the filter purpose but does not add new details beyond 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?

Description clearly states verb 'list', resource 'city slugs', and grouping 'by country'. It distinguishes itself from siblings by noting it should be called first to discover valid slugs.

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?

Explicitly says 'Call this first to discover valid slugs before any other tool' and explains the optional country filter. Provides clear context for when to use.

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

All cityparity — Cost-of-Living & Quality-of-Life Comparison 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

A4.7/5.0
Disambiguation5/5

Each tool serves a distinct purpose: listing cities, summarizing one city, comparing two, ranking many, looking up tax regimes, and batch safety nets. Descriptions explicitly guide when to use each, eliminating ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., compare_cities, get_city_summary). The verbs are appropriate for the action, and there is no mixing of conventions.

Tool Count5/5

With 6 tools, the count is well-scoped for a cost-of-living comparison server. It covers essential operations without being too few or too many, fitting the typical 3-15 range.

Completeness4/5

The tool set covers discovery, summary, comparison, ranking, tax regimes, and safety nets. A minor gap is the lack of a detailed single-city cost breakdown (only headline costs in get_city_summary), but overall it's fairly complete.

Resources