Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Full italian companies data from VAT

get_company_IT_full
Read-onlyIdempotent

Retrieve a complete profile of an Italian company by VAT number or tax code, including officers, offices, classifications, shareholders, employees, contacts, and financial statements.

Instructions

Returns the complete and detailed profile of an Italian company.

The lookup uses a VAT number or Tax Code. - Company Data (Name, VAT Number, Tax Code, CCIAA, and REA) - Managers - Registered Office and other types of offices - Activity Classifications (New ATECO 2025, ATECO history since 2022, NACE, SIC, RAE, and SAE) - Corporate Affiliation - Exporter / Importer Status - Company Size - Company Contacts (Email, phone, fax, website, social media) - Shareholders and their ownership shares - Employees, number, trends, statistics on contract duration and types - Regarding shareholders, it is possible to access the list of the top 10 (based on ownership share size) and view their respective ownership shares. - Liquidity and profitability - Receivables and Payables - EBITDA and EBIT - Cashflow with a 2-year history - Financial fixed assets - Production value and costs - Financial revenues and expenses - Tangible, intangible, and financial assets - Net profit/loss Use get_company_IT_search to obtain VAT Args: vat_or_taxCode: VAT number or Tax Code 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_taxCode": "<vat_or_taxCode>"
    },
    "name": "get_company_IT_full"
  }
}

Input Schema

NameRequiredDescriptionDefault
vat_or_taxCodeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by enumerating what data the response contains (managers, ATECO classifications, shareholders, financials, employees), which partially substitutes for the missing output schema. It says nothing about failure behavior for invalid VAT/Tax Codes, coverage limits (e.g. data may be unavailable for small firms), or per-call cost.

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

Conciseness2/5

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

The identification of the tool and its input comes first, which is good front-loading, but the body is a ~20-item flat bullet list in which the financial entries (EBITDA, EBIT, cashflow, receivables, payables, production value, net profit) could be collapsed into one or two grouped items. The lowercase 'Use get_company_IT_search...' line is buried mid-text where routing guidance belongs at the top or bottom, not sandwiched between content bullets.

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?

With no output schema, enumerating returned fields is the right instinct and the description does it thoroughly, so an agent knows roughly what it gets back. What remains missing for a single-shot lookup tool is input format guidance and not-found/error behavior, both of which an agent needs in order to call it correctly and interpret an empty response.

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% for the single required parameter, so the description must carry the full burden. It only restates the parameter name as 'VAT number or Tax Code of an Italian company', adding no format detail such as whether the 'IT' country prefix is required, whether the checksum digit is expected, or an example value. An agent still has to guess the accepted input syntax.

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: it returns the complete, detailed profile of an Italian company keyed by VAT number or Tax Code. It is clearly distinguishable from the sibling search tool, which it explicitly names as the way to obtain a VAT. It does not, however, differentiate itself from the sibling get_company_IT_advanced, so an agent cannot tell from the description which of the two 'full/advanced' lookups to choose.

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 gives one concrete routing hint: use get_company_IT_search to obtain the VAT number first. That is useful prerequisite guidance. It offers no when-to-use vs when-not guidance relative to the other company-profile siblings (advanced, start, top), and no statement about what happens when a company is not found or is non-Italian.

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