Skip to main content
Glama
Portale Offerte MCP

Portale Offerte MCP

by marcopa84

indici_prezzi

Read-only

Retrieve historical monthly wholesale price indices for electricity and gas, such as PUN, PSV, PE, CMEM, Pfor, and Psbil, to analyze market trends over a chosen period.

Instructions

Valori mensili storici degli indici all'ingrosso: PUN (luce), PSV, PE, CMEM, Pfor, Psbil (gas).

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": "indici_prezzi"
  }
}

Input Schema

NameRequiredDescriptionDefault
ultimi_mesiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 read-only, external-data nature is covered structurally. The description adds that the values are monthly and historical, which is useful context, but says nothing about freshness, update cadence, or the shape of the returned series.

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?

A single front-loaded sentence with no filler; every clause earns its place by naming the indices. It is efficient, though its brevity contributes to the coverage gaps noted elsewhere.

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 read-only lookup with one optional parameter and annotations covering the safety profile, the description is adequate but thin. With no output schema, it should at least sketch the return structure (per-month records per index, units) and explain what the month-window parameter does.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden for ultimi_mesi, yet it never mentions the parameter at all. The name 'Ultimi Mesi' plus the default of 12 and bounds 1-120 make the schema partly self-explanatory, but the description adds no meaning beyond it.

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 the exact resource (historical monthly wholesale index values) and enumerates the specific series returned (PUN for electricity, PSV, PE, CMEM, Pfor, Psbil for gas), which clearly separates it from siblings like stima_costo or parametri_regolati. It lacks an explicit verb such as 'retrieve/return', but the data content is unambiguous.

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 statement of when this tool should be chosen over alternatives, no mention of prerequisites, and no exclusion of cases where a sibling (e.g. stima_costo for computed costs) would be the better call. Usage is only implied by the data the tool exposes.

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