Skip to main content
Glama
Sign In
SwitchAI

SwitchAI

by US1929
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

parse_energy_bill

Analyze Italian electricity or gas bills to extract supplier, POD/PDR, annual consumption, estimated annual cost, and tariff zone for tariff comparison.

Instructions

Analizza il testo di una bolletta italiana (luce o gas) ed estrae: fornitore, POD/PDR, consumo annuo, spesa annua stimata, zona tariffaria.

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": {
      "bill_text": "<bill_text>"
    },
    "name": "parse_energy_bill"
  }
}

Input Schema

NameRequiredDescriptionDefault
bill_textYesTesto completo della bolletta da analizzare. Puoi estrarre il testo da un PDF o riceverlo dall'utente.

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 present, and the description does not disclose behavioral details such as required formats, error handling, or limitations. It only states the basic extraction function, leaving the agent unaware of potential failure modes.

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?

The description is a single sentence, concise and front-loaded with the main action. However, the list of extracted fields could be structured with bullet points for clarity, but it is not overly verbose.

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?

With one parameter, no output schema, and no annotations, the description covers the basic function. However, it lacks details on accuracy, limitations (e.g., only Italian bills), or error handling, which is needed for a parsing tool of complex documents.

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?

The single parameter 'bill_text' has schema coverage at 100%. The description adds helpful context: 'Puoi estrarre il testo da un PDF o riceverlo dall'utente', which clarifies how to obtain the input, exceeding the schema alone.

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 the verb ('Analizza', 'estrae') and the resource ('bolletta italiana di luce o gas'). It lists the specific extracted fields, distinguishing it from sibling tools like 'calculate_energy_savings' or 'get_available_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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites like the input must be in Italian or from a specific source. The agent must infer from sibling names.

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