querido-diario-mcp-server

get_city

Retrieve a Brazilian municipality's details by its 7-digit IBGE territory ID, including name, state, gazette availability date, and official publication URLs.

Instructions

Retrieve one Brazilian municipality by its 7-digit IBGE territory ID.

Use this when the exact territory_id is already known (from `search_cities`, or
supplied directly) and you need that city's details: name, state, Querido Diário
availability date, and known official publication URLs. If you only have a city
name, call `search_cities` instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`territory_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`level`	No
`state_code`	Yes
`territory_id`	Yes
`territory_name`	Yes
`publication_urls`	No
`availability_date`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 1, 2026

TDQS

A4.7/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden. 'Retrieve' signals a read-only lookup, and the description discloses what the result contains: name, state, availability date, and official publication URLs. It does not discuss not-found behavior, but for a simple single-ID lookup this is acceptable.

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 short, front-loaded with the primary action, and every sentence is informative. The usage guidance and alternative routing are placed after the purpose without padding.

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?

The tool is simple: one required parameter, no nested objects, an output schema exists, and the description names the only two sibling tools. It covers what the tool returns, when to use it, and when not to use it. Nothing essential is missing for an agent to call it correctly.

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?

The schema only lists territory_id as a plain string with no description. The description compensates by explaining it is a 7-digit IBGE territory ID and that it typically comes from search_cities. This gives the agent enough semantic grounding to select and format the parameter.

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: 'Retrieve one Brazilian municipality by its 7-digit IBGE territory ID.' The phrase 'one' and the ID-based lookup clearly distinguish it from the fuzzy/name-based sibling search_cities.

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 when to use this tool: when the exact territory_id is already known. It also names the alternative and its trigger: 'If you only have a city name, call search_cities instead.' This is direct routing guidance.

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

Deploy Server