Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Download Italian Company Official Document

download_italian_company_official_document

Download official Italian company documents after a status check confirms data is available, returning file links, contents, and expiration details.

Instructions

Download a document when the "stato_richiesta" of a get_italian_company_official_document call is "Dati disponibili" Response is a json containing one or more files with attributes: file_name, file_size, download_link, content, expire.

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": {
      "document_id": "<document_id>",
      "document_url": "<document_url>"
    },
    "name": "download_italian_company_official_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYesthe value id in return of a previous request.
document_urlYesthe value id in return of a previous request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the response shape (JSON with file_name, file_size, download_link, content, expire) and hints at link expiry via the 'expire' attribute, but says nothing about permission requirements, error behavior when the document is not yet available, or whether download_links are single-use.

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 sentences, front-loaded with the trigger condition, and no filler. The trailing attribute list is a bit raw but is the only place the return shape is documented, so it earns its place.

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?

With no output schema and no annotations, the description must cover both return shape and behavior. It documents the returned attributes but not their semantics (e.g., what 'content' contains versus 'download_link', how long the link lives), and gives no failure-mode information, leaving meaningful gaps for a workflow-dependent tool.

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?

Schema coverage is 100%, so baseline is 3, and the description adds context by indicating these values come from a previous get_italian_company_official_document call. It does not, however, disambiguate document_id versus document_url — the schema gives both parameters the identical (and apparently copy-pasted) description, a gap the description leaves unaddressed.

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?

States a specific verb and resource ("Download a document") and ties it to a concrete precondition on a named sibling tool ("when the stato_richiesta of a get_italian_company_official_document call is 'Dati disponibili'"). An agent can tell this is the second step of a two-call workflow and distinguish it from the sibling that returns the status.

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?

The trigger condition is explicit and effectively implies the negative case (do not call before the status is 'Dati disponibili'). It provides no guidance on what to do if the state is different, nor any prerequisites such as where document_id/document_url originate, so it falls short of full when/when-not/alternatives guidance.

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