Skip to main content
Glama
Sign In
Portale Offerte MCP

Portale Offerte MCP

by marcopa84
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

dettaglio_offerta

Read-only

Retrieve full details for an Italian electricity or gas offer by its code, including tiered prices, discounts, contract terms, coverage zones, and seller contacts.

Instructions

Mostra tutti i dettagli di un'offerta: prezzi per fascia, sconti, condizioni contrattuali, zone e contatti.

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": {
      "codice": "<codice>"
    },
    "name": "dettaglio_offerta"
  }
}

Input Schema

NameRequiredDescriptionDefault
pivaNoPartita IVA del venditore, se lo stesso codice e usato da piu venditori
codiceYesCodice offerta restituito da cerca_offerte

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 safety is covered. With no output schema, the description's enumeration of returned sections (prices, discounts, contract terms, zones, contacts) usefully discloses the response shape, but says nothing about behavior when an offer code is unknown, piva disambiguation, or external lookup implications of openWorldHint.

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 a compact colon-delimited enumeration of returned data; every element is informative. The list of fields is slightly long but earns its place given there is no output schema.

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 2-parameter read-only detail lookup with full schema coverage, the description covers purpose and response content adequately. Remaining gaps (missing-code behavior, piva disambiguation) are minor given the rich schema.

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%, with both 'codice' and 'piva' documented in the schema, including the note that codice comes from cerca_offerte. The description adds no meaning beyond that, so the baseline 3 applies.

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 gives a specific verb+resource ("Mostra tutti i dettagli di un'offerta") and enumerates the content returned (prices by tier, discounts, contract conditions, zones, contacts), so the agent knows exactly what this yields. It does not name or contrast with siblings like cerca_offerte in the description text itself (that link only appears in the schema), so it falls short of 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?

There is no explicit when-to-use/when-not guidance or named alternative in the description. Usage is only implied by the word "dettaglio" — a single-offer lookup that presumably follows a search — which the agent must infer.

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