Skip to main content
Glama
Sign In
Solematica

Solematica

by n3m1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

prezzi_energia

Retrieve current Italian electricity prices (PUN, ARERA) with update dates. Calculate energy savings and compare providers using real-time rate data without API keys.

Instructions

Restituisce i prezzi correnti dell'energia elettrica in Italia (PUN, ARERA) con data di aggiornamento. Utile per calcoli di risparmio e confronti. Non richiede API key.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.7/5.0
Behavior3/5

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

Discloses authentication requirements ('Non richiede API key') and output metadata ('con data di aggiornamento'), but omits rate limits, caching behavior, or real-time vs delayed data details.

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 well-structured sentences with zero fluff: immediate action statement followed by use case and auth note.

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?

Adequately covers simple retrieval scope by specifying geographic scope (Italia), price types (PUN/ARERA), and temporal metadata despite lack of output schema.

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?

Zero-parameter tool meets baseline; description correctly implies no configuration needed via 'Non richiede API key' and absence of parameter mentions.

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?

Specific verb ('restituisce') and resource ('prezzi correnti dell'energia elettrica'), with technical distinctions (PUN, ARERA) that differentiate it from sibling provider comparison tools.

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?

Implies usage context ('Utile per calcoli di risparmio e confronti') but lacks explicit when-not-to-use guidance or contrast with 'confronta_provider'/'dettaglio_provider'.

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