Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Check if Italian Fiscal Code is real and existent in the official database

check_IT_fiscal_code
Read-onlyIdempotent

Verify whether an Italian Fiscal Code is real and exists in the official database, helping confirm a person's fiscal code before use.

Instructions

Check if an Italian Fiscal Code is real and existent in the official database. Args: fiscalCode: fiscal code of an italian person

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": {
      "fiscalCode": "<fiscalCode>"
    },
    "name": "check_IT_fiscal_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
fiscalCodeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and idempotency need no restating. The description adds one genuinely useful behavioral fact that the annotations do not convey: the check is against an 'official database', i.e. an existence check rather than a checksum/format-only validation. It says nothing about error behavior, rate limits, or what the tool returns, which limits it to a 3.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is front-loaded and waste-free, but the docstring-style 'Args: fiscalCode: ...' block is boilerplate that adds no information beyond the schema property name. It is short, yet part of that brevity comes from under-specification rather than tight writing.

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?

For a single-parameter read-only tool this is nearly adequate, but there is no output schema, so the description should say what a result looks like (boolean, status, or derived personal data such as birth date and sex, which fiscal-code lookups commonly return). That missing return-value context and the absent input format are real gaps.

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 description coverage is 0%, so the description must carry parameter meaning, and it only restates the name: 'fiscal code of an italian person'. There is no format guidance (length, alphanumeric pattern, omocodia handling, case sensitivity) and no example, leaving an agent likely to guess at input shape.

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 and resource: verify whether an Italian fiscal code is real and exists in an official registry. This is unambiguous and clearly distinct from the company/document siblings, which do not validate fiscal codes. It falls short of a 5 only because it never contrasts itself with any related validation tool.

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?

The description implies the use case (input a fiscal code, learn whether it exists) but gives no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no mention of what a failure result means. No alternatives are named, so the agent must infer everything from the tool name.

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