Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Find It Istat By Comune Name

find_IT_istat_by_comune_name

Retrieves the ISTAT code for an Italian municipality by its name, enabling lookups of official municipal identifiers for data matching and reporting.

Instructions

Searches for the ISTAT code associated with a given Italian municipality.

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": {
      "comune": "<comune>"
    },
    "name": "find_IT_istat_by_comune_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
comuneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full burden and does not say what is returned (a code string? an object?), how ambiguous or partial municipality names are handled, whether matching is case/accent sensitive, or what happens when no match is found.

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 short, front-loaded sentence with no filler; the key resource (ISTAT code) appears early. It is efficient but leaves little room for the details an agent needs.

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

Completeness2/5

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

A lookup tool with no annotations, no output schema, and an undocumented parameter needs the description to explain the return value and no-match behavior, and it does neither. The definition is under-specified for correct invocation.

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?

The single parameter 'comune' has 0% schema description coverage, and the description only says 'a given Italian municipality' without specifying format expectations such as accents, case, or inclusion of province qualifiers. It does not compensate for the undocumented parameter.

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 (searches) and resource (ISTAT code for an Italian municipality), which is distinguishable from the reverse lookup sibling find_IT_municipality_by_istat. It does not explicitly name that sibling, so the differentiation is inferable rather than stated.

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?

Usage is only implied: use this when you have a municipality name and need its ISTAT code. There is no explicit when-to-use/when-not statement and no pointer to the inverse tool find_IT_municipality_by_istat for going from code to name.

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