Portugal (public data)

power_cuts

Planned power cuts (E-REDES maintenance works) for a postal code, municipality or parish.

Args: postal_code: "2795-082" for that street, or "2795" for the whole postal area. municipality: e.g. "Sintra", "Vila Nova de Gaia". parish: e.g. "Algés" (matches part of the parish name). days: how far ahead to look (max 60). With nothing given, returns a national summary by municipality.

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

Input Schema

Name	Required	Description	Default
`days`	No
`limit`	No
`parish`	No
`postal_code`	No
`municipality`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A4.2/5.0

Behavior3/5

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

There are no annotations, so the description carries the full disclosure burden. It names the upstream source (E-REDES maintenance works) and caps the lookahead at 60 days, but never states that this is a read-only call, how fresh the data is, or whether cancelled/completed works appear. Adequate but not thorough for an unannotated tool.

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?

One front-loaded summary sentence followed by a compact Args block, with no filler or repetition. Every line adds either scope or a usable example value.

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?

An output schema exists, so return values need not be described, and the geographic scoping hierarchy is fully explained. The only material gap is the undocumented 'limit' parameter and its relationship to 'days' (how many records vs. how far ahead).

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 coverage is 0%, so the description must document the five parameters, and it does well for four of them: concrete postal code formats ('2795-082' vs '2795'), example municipality and parish values, partial-name matching for parish, and the max-60 constraint on days. The 'limit' parameter is never mentioned, leaving one of five params undocumented in both schema and description.

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 opens with a specific verb+resource: planned power cuts from E-REDES maintenance works, scoped to a postal code, municipality or parish. The 'planned / maintenance works' qualifier implicitly separates it from an emergency-incident style tool, so an agent knows exactly what data it returns.

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?

The description makes the selection logic clear: pass postal_code, municipality or parish to narrow the search, and with nothing given it returns a national summary by municipality, which is a genuine usage instruction rather than a restatement. It lacks explicit when-not guidance or a named alternative (e.g. a live-incidents tool) for current outages.

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) tools Inspect

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.