Skip to main content
Glama

Figures for a city

get_city
Read-onlyIdempotent

One city's figures, each with source, period, geographic level and licence; daylight; the take-home pay model; whether each person in a household may live and work there, with the rules checked; links to sources we may not copy, and Borgo's generic quality-of-life index with its fixed weights. Compact by default (figures with a value, long series counted); pass metrics for a few figures, detail "full" for everything.

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

Input Schema

NameRequiredDescriptionDefault
cityYesCity id or name
detailNo"summary" (default) or "full"
rightsNoOptional: each person's rights to live and work that are not citizenship, in the same order as passports, e.g. [[{kind:'permanent',where:'DE'}]]
metricsNoOnly these metric ids, e.g. ['rent_1bed','pm25']; list_metrics_and_sources kind "metrics" lists them
passportsNoOptional: each person's passports, e.g. [['US']] or [['IT'],['US','IE']]: who may live and work there

Output Schema

NameRequiredDescriptionDefault
cityYes
noteYes
detailYes
rightsYes
figuresYes
reportVersionYesThe report's shape version (now 2.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), yet the description still adds non-trivial behaviour: the default response truncates long series ("long series counted"), detail="full" expands everything, rights are actually adjudicated ("with the rules checked"), the index uses fixed weights, and some source links are not redistributable. The opaque phrase "long series counted" and the absence of any cost/size warning keep it from a 5.

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, no filler: the first enumerates the payload, the second delivers the sizing rule and the escape hatch. The semicolon chain is dense, but every clause carries distinct content and the operational guidance sits at the end where it is easy to find.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full input schema and an output schema, the description needn't explain return fields, and it correctly focuses on content scope and default sizing. Still missing for a 5-parameter tool whose output can be large: what happens with an unknown city id, and how the compact/long-series truncation manifests in the response.

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 description coverage is 100%, including detailed enum documentation for rights kinds and the work/until/where subfields, so the baseline is 3. The description only restates the metrics and detail behaviour already documented in the schema and adds no meaning for passports or rights ordering beyond what the schema says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes the resource unmistakable: one city's figures, plus daylight, take-home pay, residence/work rights checking, source links and a quality-of-life index. The verb is only implied ("One city's figures") rather than stated, and no sibling such as compare_cities is named, so an agent knows what it returns but must infer the operation from the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Compact by default ... pass metrics for a few figures, detail 'full' for everything" gives real guidance on how to size a call, and it points at list_metrics_and_sources to discover metric ids. But there is no statement of when to prefer this over compare_cities or community_figures, and no exclusion conditions; usage is only implied.

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.