Skip to main content
Glama
Portale Offerte MCP

Portale Offerte MCP

by marcopa84

elenco_venditori

Read-only

Lists Italian energy sellers with active offer counts per commodity, optionally filtered by seller name or VAT number and by electricity, gas, or dual offers.

Instructions

Elenca i venditori presenti nel Portale Offerte con il numero di offerte attive per commodity.

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

Input Schema

NameRequiredDescriptionDefault
testoNoParte del nome o partita IVA
commodityNoSolo venditori con offerte di questa commodity

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 profile is covered. The description adds value by disclosing what the result contains (vendor plus active-offer count per commodity), which matters since there is no output schema, but it says nothing about result size, sorting, or whether inactive vendors are included.

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?

A single front-loaded sentence with no filler; the resource and the returned value are both stated up front.

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 two-optional-parameter read-only lookup with no output schema, the description adequately conveys purpose and return content. The remaining gap is operational detail (result limits, ordering, whether filtering combines) rather than anything blocking a correct call.

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%, so 'testo' (name or VAT fragment) and 'commodity' are already documented structurally. The description only echoes the commodity dimension ('per commodity') and adds no matching semantics such as substring vs exact matching or combination behavior. Baseline 3 applies when the schema carries the parameter burden.

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?

States a specific verb ('Elenca') and resource ('venditori'), scopes it ('presenti nel Portale Offerte') and previews the payload ('numero di offerte attive per commodity'). It is clearly distinguishable from cerca_offerte or dettaglio_offerta by resource, but never names a sibling to make the contrast explicit.

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 to use this versus cerca_offerte, stima_costo or the other siblings, and no note on prerequisites or ordering of calls. The only hint of usage is implicit in the enumeration framing.

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