Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Get Company It Legal Forms List

get_company_IT_legal_forms_list

Retrieves updated Italian legal form codes and descriptions, helping you find valid legalFormCode values for Italian company searches.

Instructions

Returns the updated Italian legal form codes and descriptions.

Use this tool together with get_company_IT_search to discover the accepted legalFormCode values.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_company_IT_legal_forms_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, but the operation is a zero-parameter static lookup so the risk profile is inherently low. It discloses the payload contents (codes plus descriptions) and the 'updated' nature of the data, but says nothing about output shape, ordering, or whether the list is cached/occasionally refreshed.

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

Conciseness5/5

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

Two short sentences with zero filler. The statement of what is returned comes first, and the integration hint with the sibling follows, which is the right order for an agent scanning for purpose before usage.

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?

For a no-param, no-output-schema lookup tool, the description covers both what it returns and why an agent would call it. A minor gap is the absence of any note on output format or freshness cadence, but nothing essential to a correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing to disambiguate; the baseline of 4 applies. The description correctly adds no param discussion, instead spending its words on the return content and how to use it.

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 names a specific verb and resource (returns Italian legal form codes and descriptions), which is precise enough to separate it from the geographic and company-search siblings. It does not explicitly state what it is not, but the resource is unique among the listed tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete usage context: pair it with get_company_IT_search to discover accepted legalFormCode values. That tells the agent both the moment to call it (before searching/filtering by legal form) and the downstream consumer of its output, though it offers no explicit when-not guidance.

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