Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Get It Metropolitan Cities List

get_IT_metropolitan_cities_list

Retrieve the list of Italian metropolitan cities for address validation, regional analysis, and administrative data workflows.

Instructions

Returns the list of Italian metropolitan cities

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_IT_metropolitan_cities_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 burden. It implies a safe, static read ("Returns the list") but says nothing about whether results are ordered, how large the list is, or what each entry contains. For a zero-parameter reference list the risk is low, so this is adequate but thin.

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?

One short sentence with the resource front-loaded and zero filler. Nothing could be removed without losing meaning.

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

Completeness4/5

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

For a zero-argument static lookup with no output schema, the description is nearly complete; the only gap is that it does not hint at what fields each metropolitan city entry returns, which would help an agent decide whether to call it versus a richer search tool.

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 tool takes no parameters and the schema is an empty object with additionalProperties false, so there is nothing for the description to disambiguate. Baseline 4 applies.

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?

"Returns the list of Italian metropolitan cities" gives a specific verb (returns) and a specific resource (Italian metropolitan cities), which is enough to separate it from provinces, regions, and municipality lookups in the sibling set. It does not explicitly name any sibling, so differentiation is inferred from the resource name 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 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 prerequisites, and no pointer to alternatives such as get_IT_provinces_list or get_IT_regions_list for adjacent geographic lookups. The agent must infer usage purely from the resource name.

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