Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Find It Municipalities By Zip

find_IT_municipalities_by_zip

Retrieve Italian municipalities and their ISTAT codes from a ZIP code to validate addresses and support location-based lookups.

Instructions

Retrieves the list of Italian municipalities and their ISTAT code based on the ZIP code.

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": {
      "zip_code": "<zip_code>"
    },
    "name": "find_IT_municipalities_by_zip"
  }
}

Input Schema

NameRequiredDescriptionDefault
zip_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the return payload (municipality list plus ISTAT codes) but says nothing about permissions, whether the lookup can return multiple or zero results, or how the ZIP is validated.

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?

One well-formed sentence that front-loads the resource and ends with the input constraint. No filler, though the brevity leaves gaps elsewhere.

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?

A simple one-parameter lookup with no output schema, and the description does say what comes back. Still missing the ZIP format contract and cardinality expectations, which matter for an agent constructing the call.

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%, so the description must define the single parameter. It only restates that a ZIP code is required; the Italian CAP format (5 digits, leading zeros, string type) and expected input shape are never specified.

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?

States a specific verb ('Retrieves'), resource ('Italian municipalities and their ISTAT code') and the lookup key ('based on the ZIP code'). That key distinguishes it from the name-based and ISTAT-based sibling lookups, though the description never names an alternative 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?

No guidance on when to choose this lookup versus find_IT_istat_by_comune_name or find_IT_municipality_by_istat, and no note about the case where a ZIP covers multiple municipalities or is invalid.

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