Skip to main content
Glama
Sign In

Portugal (public data)

by io.github.ThiagoJacobLannes
OverviewDiscussionsAdmin

electricity_price

Portugal's day-ahead wholesale electricity price (OMIE), per 15-minute period, in €/MWh.

Useful for indexed ("dynamic") tariffs: when is electricity cheapest to run the washing machine or charge the car. Not the retail price on a normal bill. Args: day: ISO date, e.g. "2026-11-10". Default: the most recent day OMIE has published. cheapest: also list this many cheapest periods (max 12).

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

Input Schema

NameRequiredDescriptionDefault
dayNo
cheapestNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it discloses 15-minute granularity, €/MWh units, the default day ("the most recent day OMIE has published"), and a hard cap of 12 on `cheapest`. It doesn't describe behavior for future/unpublished dates or publication lag, which would complete the picture for a data-fetch tool.

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?

Front-loaded with the resource definition, then usage, then params — the ordering an agent needs. The washing-machine/car example is illustrative rather than padding. Slightly loose prose, but no sentence is wasted.

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-parameter read tool with an output schema (so return shape is covered elsewhere), the description supplies units, granularity, defaults, and intended use. Timezone and handling of days with no published data are the only notable omissions.

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?

Schema description coverage is 0%, so the description must compensate, and it does: `day` is defined as an ISO date with an example plus the default-to-latest behavior, and `cheapest` gains meaning (also list the N cheapest periods) that the bare integer schema lacks. Minor gap: it caps `cheapest` at 12 but doesn't restate the schema default of 4 or say how the cheapest list interacts with the main series.

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?

"Portugal's day-ahead wholesale electricity price (OMIE), per 15-minute period, in €/MWh" names the exact resource, market, granularity, and unit in one clause, and explicitly excludes the retail bill price. An agent knows precisely what data comes back without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete when-to-use scenario (indexed/dynamic tariffs, deciding when to run appliances) and an explicit scope exclusion ("Not the retail price on a normal bill"). It stops short of naming an alternative tool for retail pricing, but the exclusion does the routing work.

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

All Portugal (public data) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources