Skip to main content
Glama
Sign In
Portale Offerte MCP

Portale Offerte MCP

by marcopa84
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

stato_dati

Read-only

Shows the current open-data status—data date, offer count, cache folder, and terms of use—and can force a fresh download from the portal.

Instructions

Data dei dati in uso, numero di offerte, cartella della cache e condizioni d'uso degli open 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": "stato_dati"
  }
}

Input Schema

NameRequiredDescriptionDefault
aggiornaNoForza un nuovo scaricamento dal portale

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and network profile is partly supplied. The description confirms the tool reports local/cached state (cache folder) and open data license terms, which adds some context, but it never mentions that a refresh can trigger a network download or what that costs.

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

Conciseness3/5

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

One short sentence with no padding, so it is appropriately sized. However, the opening 'Data dei dati in uso' is redundant and the sentence is a comma-list of return fields, leaving the actual action unstated rather than front-loading a clear purpose.

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, the description does correctly carry the return-value burden by naming four kinds of state returned. It remains incomplete about response shape, refresh behavior, and how the data relates to siblings, which matters for a status tool in a seven-tool family.

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 100% with a single optional boolean whose description ('Forza un nuovo scaricamento dal portale') is fully documented in the schema. The description adds no meaning about when to set the refresh flag; baseline 3 applies since the schema carries the parameter burden.

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

Purpose3/5

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

The description enumerates the state it reports (data date, offer count, cache folder, open data terms of use) but contains no verb and never says plainly that this is a status/info tool. An agent can infer the purpose from the enumerated contents, but the phrasing 'Data dei dati in uso' is awkward and circular rather than a specific verb+resource statement.

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?

There is no when-to-use guidance at all, no prerequisites, and no mention of alternatives. Sibling names like controlla_aggiornamenti and parametri_regolati plausibly overlap with this tool, yet nothing routes the agent between them.

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

Deploy Server

Other Tools