SiteCheck Company Records

Italian public procurement datasets from ANAC open data

gov_anac_italy_procurement

Read-only

Italian public procurement datasets from ANAC open data (dati.anticorruzione.it, CKAN): dataset title, publisher, licence, last modified date, number of resources and dataset link, for a search term. Catalogue metadata only, not the tender records. Related tools on this server, for a different need: gov_dati_gov_it_italy_open_data when you need Italian open government datasets from dati.gov.it: title; gov_ted_eu_procurement when you need EU public procurement notices from TED, filtered by buyer. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "gov_anac_italy_procurement"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Search text, 2 to 80 characters (Italian or English)
`rows`	No	Datasets to return, 1 to 10 (default 5)

Output Schema

Name	Required	Description	Default
`query`	No
`source`	No
`datasets`	No
`checkedAt`	No
`totalDatasets`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description reinforces the read-only scope by stating it returns catalogue metadata rather than tender records. It adds genuine non-annotation context: the price ($0.002 USDC per successful call via x402 on Base, Solana or Arc) and that failed calls are not charged — a material detail for call budgeting. It stops short of describing result ordering or what an empty match looks like, but the output schema carries return-shape information.

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?

The core capability and the metadata-only scope are front-loaded in the first two sentences, followed by sibling routing and pricing. Nearly every clause earns its place, though the pricing parenthetical (three payment chains plus the $0.002 figure) is dense enough to slightly burden scanning.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, read-only catalogue search with a full schema and an output schema, the description covers source, returned fields, scope limits, alternatives and cost. Nothing an agent needs to decide to call it, or to predict what comes back, is 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 100%, with both q (2–80 chars, Italian or English) and rows (1–10, default 5) already documented. The description adds only that the query is 'for a search term', which does not extend meaning beyond the schema; the baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific source (ANAC open data at dati.anticorruzione.it, CKAN) and the exact fields returned: dataset title, publisher, licence, last modified, resource count and link. It also draws a sharp boundary — 'Catalogue metadata only, not the tender records' — so an agent cannot confuse it with a tender-record search.

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

Usage Guidelines5/5

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

It explicitly routes the agent to two alternatives with conditions: gov_dati_gov_it_italy_open_data for Italian open government datasets from dati.gov.it, and gov_ted_eu_procurement for EU procurement notices from TED filtered by buyer. The framing 'Related tools on this server, for a different need' makes the exclusion criterion explicit rather than implied.

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

All SiteCheck Company Records tools Inspect

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

Need Help?