Skip to main content
Glama
Sign In
Solematica

Solematica

by n3m1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dettaglio_provider

Retrieve detailed profiles of Italian solar providers including prices, components, warranties, financing, and accessory services. Access photovoltaic operator data by slug without API key.

Instructions

Restituisce la scheda completa di un operatore fotovoltaico italiano: prezzi, componenti, garanzia, finanziamento, servizi accessori (pompa di calore, wallbox, caldaia), contatti e descrizione. Non richiede API key.

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": {
      "slug": "<slug>"
    },
    "name": "dettaglio_provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSlug del provider (es. 'iren', 'enel', 'plenitude', 'otovo', 'eon', 'hera', 'a2a', 'edison', 'engie', 'sorgenia', 'bluenergy')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4/5.0
Behavior4/5

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

Discloses 'Non richiede API key' and enumerates returned data fields (prezzi, componenti, garanzia), compensating for missing annotations and output schema.

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 compact sentences: first front-loaded with complete data taxonomy, second notes auth requirement. No redundancy.

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?

Without output schema, comprehensively lists return data categories (finanziamento, servizi accessori, contatti) providing sufficient invocation context.

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 has 100% coverage with examples; description adds no parameter detail but meets baseline since structured documentation is complete.

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?

Specific verb (restituisce) + resource (scheda completa operatore fotovoltaico) clearly distinguishes from siblings like confronta_provider (comparison) and cerca_articoli (search).

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?

Implicitly suggests use for single-provider deep dives vs comparison, but lacks explicit when-to-use/when-not-to-use guidance relative to confronta_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