Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Start italian companies data from VAT

get_company_IT_start
Read-onlyIdempotent

Retrieve an Italian company's tax code, VAT code, name, address, activity status, SDI code, and registration date using its VAT or tax code.

Instructions

Returns taxCode, companyName, vatCode, address, activityStatus, sdiCode, registrationDate 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_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
vat_or_taxCodeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 safety behavior is covered by structured data. The description adds value by listing the exact response fields (taxCode, companyName, vatCode, address, activityStatus, sdiCode, registrationDate), which matters because no output schema exists. It says nothing about behavior on an unknown VAT/tax code, error modes, or why the name says 'start'.

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 short lines, front-loaded with the return payload and then the input, with no filler. The 'Args:' block partially restates the schema and the wording is slightly rough ('an italian company', lowercase), but nothing is wasted.

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?

Because there is no output schema, the field enumeration is essential and present, which makes the definition usable for a simple lookup. It remains incomplete on the ambiguities that matter for a tool named 'start' (synchronous vs. asynchronous result, not-found behavior) and on how it relates to the richer IT company siblings.

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% and the single parameter is just typed as a bare string, so the description carries the burden; it does explain that the field accepts either a vatCode or a taxCode, which is real meaning beyond the schema. It stops short of giving expected formats (e.g. numeric VAT length vs. alphanumeric tax code), so an agent still lacks validation guidance.

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 ... of an italian company from vatCode or taxCode') and enumerates the returned fields, which is unusually concrete. It does not, however, differentiate itself from close siblings such as get_company_IT_advanced, get_company_IT_full, or get_company_IT_search, so an agent cannot tell from the text alone why it should pick this 'start' variant.

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?

Usage is only implied by the phrase 'from vatCode or taxCode'; there is no explicit statement of when to use this instead of the advanced/full/search Italian company tools, and no prerequisites or failure conditions are given. An agent must guess at the routing decision.

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