Skip to main content
Glama
Sign In
Schema.gov.it MCP Server

Schema.gov.it MCP Server

Official
by italia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Provinces

list_provinces
Read-onlyIdempotent

Retrieve Italian provinces with their ISTAT codes, car plate abbreviations, and metropolitan city status. Filter by province name or language preference.

Instructions

List Italian provinces with their codes (ISTAT, car plate, metropolitan city).

Args:

  • keyword: (optional) Filter by province name (case-insensitive)

  • lang: "it" | "en" | "any" (default: "any")

Returns:

  • List of provinces with notation (ISTAT code), name, sigla (car plate), and metro code (if metropolitan city)

Note: Runs 3 parallel queries for names, car plates, and metro codes, then joins client-side. There are ~107 provinces, 14 of which are 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": "list_provinces"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoPreferred name language; "any" keeps all languages.any
keywordNoFilter by province name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint, and openWorldHint. The description adds behavioral transparency by stating it runs 3 parallel queries and joins client-side, and gives specific counts of provinces and metropolitan cities. No contradictions.

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?

The description is well-structured with Args and Returns sections, and the Note adds useful context. It is not overly verbose but could be slightly more concise.

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

Completeness5/5

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

Given no output schema, the description adequately explains return fields (ISTAT code, name, sigla, metro code). It also describes the parallel query execution and counts, making the tool's behavior fully understandable.

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?

Schema coverage is 100% with both parameters described. The description adds extra semantic value: keyword is case-insensitive, and lang default behavior is clarified. This goes beyond the schema's enum and default.

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

Purpose5/5

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

The description clearly states it lists Italian provinces with their codes, using specific verbs and resource (list provinces). It distinguishes itself from sibling tools like list_municipalities, list_ontologies, or list_identifiers by focusing on provinces.

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?

The description explains what the tool does and optional arguments but does not provide guidance on when to use this tool vs alternatives. No explicit when-to-use or when-not-to-use context is given.

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

Deploy Server

Other Tools