Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Get Italian Company Official Documents List

get_italian_company_official_documents_list

Lists available official Italian company registry document endpoints for a given VAT number or tax code, helping you choose the correct document to retrieve next.

Instructions

Returns the list of available official company registry document endpoints for a company, identified by its VAT number or tax code. Use with get_italian_company_official_document. Args: vat_or_taxCode: vatCode or taxCode of an italian company

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": {
      "vat_or_tax_code": "<vat_or_tax_code>"
    },
    "name": "get_italian_company_official_documents_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
vat_or_tax_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. 'Returns the list' implies a safe read and discloses that the output is a set of available endpoints rather than the documents themselves, which is useful behavioral context. However, nothing is said about permissions, whether the list varies by company type, or what the entries contain beyond being 'endpoints'.

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?

Two compact sentences with the core behavior front-loaded and the companion-tool hint placed after it. The 'Args:' block is slightly redundant given the one-parameter schema, but nothing is padded.

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 tool with no output schema, the description should convey the shape of what comes back so an agent knows how to chain into the retrieval tool. It says 'endpoints' but not what identifiers or fields the list entries carry, leaving a modest but real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It does explain that the single parameter accepts either a VAT code or a tax code for an Italian company, which is genuine added meaning. But it writes the argument as 'vat_or_taxCode' while the schema property is 'vat_or_tax_code', and gives no format or example values.

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: returns the list of available official company registry document endpoints for a company. The identification method (VAT number or tax code) is included, which lets an agent distinguish it from get_italian_company_official_document, though the differentiation is only implied by 'Use with' rather than spelled out.

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?

Points to get_italian_company_official_document as the companion tool, implying this is the discovery step that precedes retrieval. It does not say when to prefer this over download_italian_company_official_document or other registry-list siblings, and no prerequisites or exclusions are stated.

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