Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Get It Provinces List

get_IT_provinces_list

Retrieve the list of Italian provinces to support address forms, regional lookups, and location-based workflows.

Instructions

Returns the list of Italian provinces

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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, the description carries the full burden and barely does so. "Returns" implies a read-only list, but it says nothing about ordering, whether entries are names or codes, completeness, or whether the call is cheap or cached.

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 short sentence with no wasted words, front-loaded. It is efficient but so minimal that brevity comes at the cost of substance rather than from tight editing.

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?

The tool is inherently simple, but with no output schema and no statement of what each entry contains (denomination, ISTAT code, parent region), the description leaves the return shape undefined. A single clause about the returned fields would close the gap.

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 zero parameters, so there is no parameter semantics to explain; the schema is empty and fully covered. Baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Returns the list of Italian provinces" names a specific verb and resource, but it is essentially a restatement of the tool name and title. It does nothing to distinguish this from sibling lookups such as get_IT_regions_list or get_IT_metropolitan_cities_list, which an agent could easily confuse with provinces.

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 guidance on when to call this versus the regions or metropolitan-cities lookups, and no mention of prerequisites, cost, or context. The agent must infer everything from the name alone.

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