Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Get Italian Company Official Document

get_italian_company_official_document

Fetches an official Italian company registry document (visura camerale) using a VAT number or tax code and document URL.

Instructions

Retrieves an official company registry document (visura camerale) for a company identified by its VAT number or tax code. Args: document_url: url of the requested document 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": {
      "document_url": "<document_url>",
      "vat_or_tax_code": "<vat_or_tax_code>"
    },
    "name": "get_italian_company_official_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_urlYes
vat_or_tax_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and does not meet it. It never says whether the document is returned inline, as a link/blob, whether the call is asynchronous, whether it requires prior authorization or consumes credits, or how it differs behaviorally from the sibling download tool.

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 prose sentence is front-loaded and tight, and the 'Args:' block is short and informative. The Args block is a docstring artifact that partly duplicates the schema property names, but given the 0% schema coverage it earns its space.

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 two-parameter retrieval tool with no annotations and no output schema, the description explains inputs adequately but omits the most decision-relevant fact: what the caller actually receives back (file, URL, base64, JSON payload). That gap leaves an agent unable to plan around the result.

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 description coverage is 0%, so the description must compensate, and it does partially by explaining both parameters (document URL, Italian company VAT/tax code). However, it gives no format guidance for either, and it writes 'vat_or_taxCode' while the schema field is 'vat_or_tax_code', which can cause a mismatched argument name.

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?

The description uses a specific verb+resource pair, naming the artifact ('official company registry document (visura camerale)') and the keying identifier (VAT number or tax code). That is enough to distinguish it from the sibling list tool, but it never explicitly contrasts with download_italian_company_official_document, which is the nearest hazard.

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?

Usage is only implied: 'url of the requested document' hints that the URL originates elsewhere (presumably the documents-list sibling), but no alternative tool is named and no when/when-not condition is stated. An agent can infer the workflow but cannot confirm it from the text.

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