cityparity

Get a one-city profile

get_city_summary

Read-onlyIdempotent

Get a concise profile of one city: currency, tax shape, headline costs (rent, groceries, transit, childcare), safety-net values (parental leave, vacation, universal healthcare), and data freshness.

Instructions

Concise profile of one city: currency, tax shape (bracket count + top rate + payroll/national insurance), headline costs (rent / groceries / transit / childcare), safety-net values (parental leave, vacation, universal healthcare), and data freshness. Lighter than compare_cities; use when the user is asking about one place rather than a comparison. Read-only, no side effects; returns a text summary plus structured JSON.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>"
    },
    "name": "get_city_summary"
  }
}

Input Schema

Name	Required	Description	Default
`city`	Yes	City slug. Use list_cities to discover valid slugs.

Output Schema

Name	Required	Description	Default
`slug`	Yes
`name`	Yes
`country`	Yes
`currency`	Yes
`compensation_index`	Yes
`tax`	Yes
`cost_snapshot`	Yes
`safety_net`	Yes
`govt_benefits`	Yes
`inbound_tax_regime`	Yes
`data_last_updated_field`	Yes
`data_year_range`	Yes
`methodology_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jun 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, destructiveHint false, idempotentHint true. The description reinforces 'Read-only, no side effects' and adds behavioral details like data freshness and the return type (text summary + structured JSON). This 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?

The description is three sentences, each earning its place: first states purpose and content, second gives usage guidance, third declares side effects and output format. No wasted words, well-structured.

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 the tool's complexity (single parameter, output schema present), the description covers all necessary context: input, output format (text + JSON), read-only nature, and data freshness. Output schema handles return details, so description is fully adequate.

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?

The description does not add meaning beyond the input schema for the single 'city' parameter. Schema coverage is 100% and includes its own description. The description mentions 'slug' implicitly but does not elaborate further. Baseline of 3 applies.

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 provides a 'concise profile of one city' with specific categories (currency, tax, costs, safety-net), and distinguishes itself from the sibling 'compare_cities' by noting it is 'lighter' and for single-place queries.

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?

The description explicitly guides usage: 'use when the user is asking about one place rather than a comparison.' It also contrasts with 'compare_cities' as a lighter alternative, giving clear context for selection.

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

Deploy Server