Skip to main content
Glama
Sign In

Openapi®

by io.github.openapi
OverviewDiscussionsAdmin

Advanced italian companies data from VAT

get_company_IT_advanced
Read-onlyIdempotent

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 observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=true, covering the safety profile. The description adds genuine value beyond that by enumerating the returned data, including the 10-year balance-sheet history and shareholders, which is the only place this return content is documented since there is no output schema. It stops short of auth, rate-limit, or error behavior, but for a read-only lookup that is a minor gap.

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 'Returns' framing is front-loaded and the Args section is separated, but the middle is a dense wall of comma-separated field names that is hard to parse. It is appropriately sized for a tool with no output schema, but the structure could be far cleaner (grouped categories, bulleted).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 sensibly compensates by listing the returned fields, and it documents the single required parameter and its dual input formats. An agent has enough to call it correctly; only input-format specifics and failure behavior are missing.

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 carry the full load: it explains that vat_or_taxCode accepts either a VAT code or a tax code of an Italian company, which the bare 'string' schema does not. However, it gives no format details (length, numeric-only, prefix conventions), so the compensation is partial.

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 (Returns) and resource (an italian company's registration, tax, and financial data) retrieved via vatCode or taxCode, and enumerates the returned fields so the agent knows the payload is rich. It does not differentiate from close siblings like get_company_IT_full or get_company_IT_advanced vs get_company_IT_start, so an agent cannot tell why to pick this over those without opening each schema.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as get_company_IT_full, get_company_IT_search, or get_company_IT_start. The only hint is the implied 'advanced = comprehensive' framing, which is not explicit routing guidance.

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

All Openapi® toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources