Skip to main content
Glama
Sign In
SwitchAI

SwitchAI

by US1929
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_available_offers

Retrieve all available electricity or gas offers from multiple suppliers, including price, contract type, and monthly fixed cost.

Instructions

Recupera tutte le offerte disponibili per Luce o Gas. Ritorna nome fornitore, prezzo, tipo (fisso/variabile), costo fisso mensile.

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

Input Schema

NameRequiredDescriptionDefault
commodityYesLUCE per elettricità, GAS per gas metano

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention that it is a read-only operation, any side effects, rate limits, or permissions needed. The description only lists return fields but lacks behavioral context.

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?

Two concise sentences with no wasted words. The description is front-loaded with the action and immediately lists key return fields. It is appropriately sized for the tool's simplicity.

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?

Given a single enum parameter and no output schema, the description provides a clear list of return fields, which is helpful for an agent. It does not explain pagination, filtering, or edge cases, but for a simple retrieval tool it is reasonably complete.

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?

The input schema has 100% description coverage for the single parameter, and the tool description reiterates the commodity types ('Luce o Gas') and adds no further semantic meaning beyond the schema. This meets the baseline but does not enhance understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it retrieves available offers for electricity or gas, and lists the returned fields (vendor name, price, type, fixed monthly cost). It uses a specific verb ('Recupera') and resource ('offerte'), and distinguishes itself from sibling tools by focusing on offers.

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?

No guidance on when to use this tool versus alternatives (e.g., calculate_energy_savings, submit_subscription). The description does not mention prerequisites or scenarios where this tool is appropriate.

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