Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Find It Municipality By Istat

find_IT_municipality_by_istat

Retrieve detailed Italian municipality data by ISTAT code, including region, province, population, cadastral code, contacts, postal codes, and fractions.

Instructions

Retrieves detailed data about an Italian municipality using the ISTAT code:

  • istat:istatCode

  • comune:municipalityName

  • regione:regionName

  • provincia:provinceName

  • prefisso:telephoneLocalPrefix

  • cod_fisco:cadastralCodeor BelfioreCode of town,

  • superficie:surfaceArea

  • num_residenti:numberOfResidents

  • nome_abitanti:inhabitantsName

  • patrono.nomepatronSaintName,

  • patrono.datapatronSaintDate,

  • municipio:municipalityAddress

  • istat_old:oldIstatCode

  • sigla_provincia:provinceAbbreviation

  • email:emailAddress

  • pec:certifiedEmailAddress

  • tel:telephoneNumber

  • fax:faxNumber

  • frazioni:fractions

  • cap:postalCodes

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": {
      "istatCode": "<istatCode>"
    },
    "name": "find_IT_municipality_by_istat"
  }
}

Input Schema

NameRequiredDescriptionDefault
istatCodeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. "Retrieves" implies a read-only operation, and the field list usefully discloses what comes back (region, province, cadastral code, PEC, fractions, postal codes). However, it says nothing about behavior on an invalid or unknown ISTAT code (empty result vs. error), authentication needs, or rate limits.

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

Conciseness3/5

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

The one-line purpose is front-loaded and clear, but the return-field list is a long run-on block with joined tokens and typos ("cadastralCodeor BelfioreCode of town", "patrono.nomepatronSaintName,") that hurt parseability. Given the absence of an output schema the list earns its space, but its formatting does not.

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 no output schema and no annotations, the description does the right thing by enumerating returned fields, which is the main completeness win. It remains incomplete on parameter format and on failure behavior for an unmatched code, both of which an agent needs to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single istatCode parameter has no type or format description in the schema. The description only restates that lookup is "using the ISTAT code"; it does not specify digit count, leading-zero handling, or whether the old ISTAT code is accepted, which matters since istat_old appears as a distinct return field.

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 names a specific verb and resource ("Retrieves detailed data about an Italian municipality") and states the lookup key (ISTAT code), which distinguishes it from the reverse-lookup sibling find_IT_istat_by_comune_name without needing to name it. It stops short of an explicit sibling contrast, but the purpose is unambiguous.

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, no statement of when NOT to use it, and no reference to alternatives such as find_IT_istat_by_comune_name or find_IT_municipalities_by_zip. The only usable signal is the implicit constraint that the caller must already hold an ISTAT code, which the agent must infer.

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