Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Advanced italian companies data from VAT

get_company_IT_advanced
Read-onlyIdempotent

Retrieve detailed Italian company records by VAT code or tax code, including legal status, addresses, shareholders, and 10-year financial statements.

Instructions

Returns taxCode, companyName, vatCode, address, activityStatus, reaCode, cciaa, atecoClassification, detailedLegalForm, startDate, registrationDate, endDate, pec, taxCodeCeased, taxCodeCeasedTimestamp, vatGroup, sdiCode, sdiCodeTimestamp, balanceSheets (turnover, employee, networt, staffCost, totalAssets.avgGrossSalary of the last 10 years), shareHolders of an italian company from vatCode or taxCode. 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_taxCode": "<vat_or_taxCode>"
    },
    "name": "get_company_IT_advanced"
  }
}

Input Schema

NameRequiredDescriptionDefault
vat_or_taxCodeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 structurally. The description adds real behavioral value by disclosing that balance sheet metrics span the last 10 years and that shareholders are included, but it is silent on failure behavior (invalid or foreign VAT code), whether a single company or list is returned, and any cost/rate considerations.

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 field enumeration is front-loaded and, given there is no output schema, the returned-attribute list earns its place. However, it reads as a raw data dump of roughly twenty comma-separated names with typos ('networt', 'shareHolders', 'staffCost' embedded mid-list), which hurts scanability compared with grouping or prioritizing the fields.

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, the description usefully stands in for return documentation by naming the fields, so an agent knows roughly what it gets. Against a one-parameter lookup this is close to sufficient, but the missing pieces are how to choose this tool over its siblings and what the response looks like on a miss, leaving it adequate rather than complete.

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%, and the schema only types the single parameter as a string. The description partially compensates by explaining that either a VAT code or a tax code is accepted and that it must belong to an Italian company, which resolves the main ambiguity. It does not give format expectations (digit counts, prefixes, country-code handling), so the compensation is incomplete.

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?

Opens with a specific verb-and-resource framing: it returns a named set of company attributes for an Italian company looked up by vatCode or taxCode. An agent can tell this is an identifier-based lookup rather than a search, but the description never distinguishes it from close siblings such as get_company_IT_full or get_company_IT_search, so the differentiation has to be guessed from names.

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 only usage instruction is the input requirement ('from vatCode or taxCode'). There is no statement of when to prefer this over get_company_IT_start, get_company_IT_full, or get_company_IT_search, and no note about what to do if an identifier is ambiguous or unknown.

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