Skip to main content
Glama
Sign In
Portale Offerte MCP

Portale Offerte MCP

by marcopa84
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

stima_costo

Read-only

Estimates and compares annual sale costs for one or more Italian electricity or gas offers, itemizing charges under standard or custom consumption profiles; excludes network fees, taxes, and VAT.

Instructions

Stima e confronta il costo annuo della parte vendita di una o piu offerte, con il dettaglio delle voci.

Esclude rete, oneri di sistema, imposte e IVA (uguali per tutte le offerte a parita di cliente).
Profilo standard per fasce: domestico F1 33%, F2 31%, F3 36%; altri usi 44%, 24%, 32%.

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": {
      "codici": "<codici>",
      "consumo_annuo": "<consumo_annuo>"
    },
    "name": "stima_costo"
  }
}

Input Schema

NameRequiredDescriptionDefault
codiciYesUno o piu codici offerta luce, oppure uno o piu codici offerta gas (non insieme: i consumi hanno unita diverse). Le dual vanno stimate tramite le loro offerte luce e gas collegate. Un codice usato da piu venditori viene stimato per ciascuno
consumo_f1NoQuota o kWh in fascia F1 (con F2 e F3 sostituisce il profilo standard)
consumo_f2No
consumo_f3No
potenza_kwNoPotenza impegnata in kW (luce)
consumo_annuoYesConsumo annuo: kWh per la luce, Smc per il gas
riferimento_indiciNoValore degli indici per le offerte variabiliultimo_mese

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=true; the description adds substantial non-obvious behavior: that rete, oneri di sistema, imposte and IVA are excluded and why (equal across offers), and the exact standard band profiles used when F1/F2/F3 are omitted. This materially shapes how an agent interprets results, though it says nothing about output format or the effect of the open-world index dependency.

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

Conciseness5/5

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

Three tight sentences, front-loaded with purpose, then exclusions, then default profiles; each sentence carries distinct information with no filler.

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

Completeness4/5

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

For a comparison tool with no output schema, the description covers what is computed, what is excluded, and the default assumptions. It could say more about the response shape (the 'dettaglio delle voci' items) and about which reference index mode to pick, but the essentials for correct invocation are present.

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?

With 71% schema coverage the schema already documents most parameters, but the description adds meaning beyond it by spelling out the default band split percentages (33/31/36 domestic, 44/24/32 other uses) that consumption_f1/f2/f3 fall back on — information the schema only alludes to. It does not clarify potenza_kw or riferimento_indici semantics, leaving some gaps.

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 opens with a specific verb and resource ('Stima e confronta il costo annuo della parte vendita') and names the scope ('parte vendita') plus the output shape ('con il dettaglio delle voci'), so an agent can tell this is a computation/estimation tool rather than a listing tool like cerca_offerte or dettaglio_offerta. It stops short of explicitly naming those siblings, which keeps it from a 5.

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

Usage Guidelines3/5

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

Usage is implied by 'confronta ... una o piu offerte', suggesting this is the tool for multi-offer cost comparison, and the schema's codici description carries the light/gas and dual-offer constraints. However, there is no explicit when-to-use vs when-not or pointer to siblings such as cerca_offerte for retrieving codes.

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