Skip to main content
Glama
Sign In
Portale Offerte MCP

Portale Offerte MCP

by marcopa84
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

parametri_regolati

Read-only

Retrieve regulated electricity and gas offer parameters such as network charges, transport, PCV, QVD, VAT, losses, and excise duties, with optional text search by commodity.

Instructions

Corrispettivi regolati pubblicati con le offerte: oneri, trasporto, PCV, QVD, IVA, perdite di rete, accise luce.

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": {
      "commodity": "<commodity>"
    },
    "name": "parametri_regolati"
  }
}

Input Schema

NameRequiredDescriptionDefault
cercaNoTesto da cercare nel nome o nella descrizione del parametro
commodityYesluce o gas

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 safe read behavior is covered. The description adds useful domain scope by listing the regulated charge components included, but does not describe return format, pagination, or how results are structured.

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 description is a single compact sentence with no wasted wording. However, it is a noun phrase rather than an action-oriented statement, which slightly reduces clarity for tool selection.

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 simple two-parameter lookup tool with no output schema, the description gives enough domain scope to understand what kind of data is involved. It still omits usage context and a basic indication of what the response contains, leaving the agent to infer too much.

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%, and the schema fully documents both parameters, including the commodity enum. The description does not add any parameter-level meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 resource (regulated charges/corrispettivi regolati) and enumerates the included components (oneri, trasporto, PCV, QVD, IVA, perdite di rete, accise luce). It lacks an explicit verb and does not distinguish this tool from siblings such as indici_prezzi or dettaglio_offerta.

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 guidance on when to use this tool versus the many sibling tools, nor any stated prerequisites or exclusions. The agent must infer its role solely from the resource name and component list.

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