Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Search italian companies by advanced search criteria

get_company_IT_search
Read-onlyIdempotent

Search Italian companies by name, location, ATECO, size, or status to find VAT numbers and retrieve paginated enriched data; use dryRun to count matches.

Instructions

Returns a list of Italian companies based on the search criteria.

Use this tool if you do not know the VAT number of a company. Use it with dryRun=1 and no limit parameter to get only the count of available results for the matching criteria. Use it to extract enriched data, paginated with skip up to 1000 records, such as name, address, PEC, start data, or advanced data.

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_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude for geographical search (optional).
pecNoPEC email address of the company (optional).
longNoLongitude for geographical search (optional).
skipNoThe number of records to skip for pagination (optional).
cciaaNoChamber of Commerce code (optional).
limitNoThe max number of results to return. To get only the total count, skip this parameter and set ``dryRun`` to 1.
dryRunNoReturns only the number of records found and the price.
radiusNoRadius in meters for geographical search (optional).
endDateNoFilter by the end date of the company (optional).
reaCodeNoREA code (optional).
sdiCodeNoSDI code (optional).
townCodeNoThe cadastral code for the town (optional).
atecoCodeNoATECO code for the company (optional).
startDateNoFilter by the start date of the company (optional).
companyNameNoThe name or part of it of an Italian company (optional).
maxTurnoverNoMaximum turnover value (optional).
minTurnoverNoMinimum turnover value (optional).
autocompleteNoSearch for strings that begin with the specified query (optional).
maxEmployeesNoMaximum number of employees (optional).
minEmployeesNoMinimum number of employees (optional).
provinceCodeNoThe 2 letter province code to restrict the results.
legalFormCodeNoFilter by company legal form. Use ``get_company_IT_legal_forms_list`` to inspect the available codes.
activityStatusNoStatus in the Chamber of Commerce. Allowed values are ``ATTIVA``, ``CESSATA``, ``REGISTRATA``, ``INATTIVA``, ``SOSPESA``, and ``IN_ISCRIZIONE``.
dataEnrichmentNoAdditional enrichment options. Allowed values are ``start``, ``advanced``, ``pec``, ``address``, ``shareholders``, and ``name``.name
creationTimestampNoFilter by creation unix timestamp (optional).
shareHolderTaxCodeNoTax code of a company member (optional).
lastUpdateTimestampNoFilter by last update unix timestamp (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/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 genuinely useful behavior beyond that: the dryRun path returns a count and a price (a cost implication an agent should know before spending credits) and the skip pagination is capped at 1000 records. It does not mention auth requirements or default page size, which keeps it from a 5.

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?

Three short, front-loaded paragraphs that move from what the tool returns to when to use it to how to page/enrich. Little wasted wording, though the trailing phrase "based on the search criteria" is redundant and the opening line repeats the title almost verbatim.

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?

For a 27-parameter search tool with no output schema and zero required parameters, the description leaves notable gaps: it never says what happens when no criteria are supplied (whether an empty search is allowed, returns everything, or errors) and it does not describe the shape of the returned records beyond listing a few enrichment fields. It covers the count-only and pagination paths well, but an agent still has to guess at the empty-criteria behavior.

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 100%, so the schema already documents all 27 parameters, establishing a baseline of 3. The description adds only marginal semantics on top — the dryRun/limit interaction is largely restated from the schema's own limit and dryRun descriptions, though the 1000-record skip cap is new information. It does not explain the dataEnrichment mode tradeoffs or how the many filters combine (AND vs OR).

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 opens with a specific verb and resource: "Returns a list of Italian companies based on the search criteria." Combined with the guidance line "Use this tool if you do not know the VAT number of a company," an agent can infer this is the discovery tool rather than a lookup-by-identifier tool. It does not name the sibling lookup tools (e.g. get_company_IT_full or get_company_IT_advanced) explicitly, so differentiation is implied rather than stated.

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 three concrete usage conditions: use when the VAT number is unknown, use with dryRun=1 and no limit to get only a count, and use to extract enriched paginated data. This is clear context for when to reach for the tool. It stops short of explicit exclusions (e.g. "do not use if you already have the VAT number — use X instead"), so it lands at 4 rather than 5.

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