Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Get Suppressed Italian Municipalities

get_suppressed_italian_municipalities

Retrieve the list of suppressed or merged Italian municipalities to identify former administrative areas and support historical or territorial data checks.

Instructions

Returns the list of suppressed or merged Italian municipalities

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_suppressed_italian_municipalities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, but it does convey the essential behavior: a read that returns a complete list and requires no arguments. It does not say whether it is paginated, how large the list is, or whether merged entries indicate their successor municipality — gaps that matter for a historical reference dataset.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler or redundancy, which is the right shape for a zero-argument list tool. It is arguably over-terse, since one more clause about what each entry contains would have cost little.

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?

There is no output schema, so the description is the only place an agent could learn the shape of a returned municipality record (name, code, province, merger target) and it omits that entirely. For a simple lookup the missing detail is not fatal, but the definition is only minimally sufficient.

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 tool takes zero parameters (empty object schema with additionalProperties false), so there is no parameter meaning for the description to add. Baseline of 4 is adjusted slightly downward because the description wastes no opportunity but also never confirms the tool takes no filters, leaving an agent to consult the schema to discover that.

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 uses a specific verb ('Returns') and a precisely scoped resource ('suppressed or merged Italian municipalities'), which tells an agent exactly what data is being retrieved. It is distinguishable from the sibling list tools (regions, provinces, metropolitan cities, zip lookups) by the 'suppressed/merged' qualifier, though it never names those alternatives explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing says why an agent would want historical/suppressed municipalities rather than the current municipality list, no mention of prerequisites, and no named alternative such as find_IT_municipalities_by_zip. The phrase 'suppressed or merged' hints at the historical use case but leaves the agent to infer it.

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