mcp

Power outages right now

get_power_status

Read-onlyIdempotent

Puerto Rico's electricity grid right now, from LUMA Energy's public outage portal: how many of the island's ~1.47 million customers are without service, as a count and a share, with LUMA's PLANNED work broken out separately so the unplanned share is readable on its own; a severity word; the seven LUMA regions each with their own count and share; the worst region; and how many towns are affected. Optionally the daily history (one ~06:00 AST reading per day) behind the weekly Grid Watch. IMPORTANT: these are LUMA's own published figures at the moment of reading, not an independent measurement, and a missing day in the history, or a day with null counts and a countsReason, is a failed read, never a zero; countsRead=false on the live reading means LUMA's count could not be read and its counts are null. Cite 787daily.com/live/power/ and LUMA Energy.

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

Input Schema

Name	Required	Description	Default
`days`	No	How many days of daily history to include (0 = none, the default; the history starts 2026-09-05)
`region`	No	Optional LUMA region to narrow to: San Juan, Bayamon, Carolina, Caguas, Arecibo, Mayaguez, Ponce

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedOct 6, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description layers on substantive behavioral context the annotations cannot: the figures are LUMA's own published numbers rather than an independent measurement, a missing history day or a null day with a countsReason is a failed read and never a zero, and countsRead=false means LUMA's count could not be read. It even specifies the required citation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and data source are front-loaded, which is good, but the opening is a single semicolon-chained run-on enumerating the entire payload, and the paragraph is long for a two-parameter read tool. The content is dense and mostly earns its place, yet the structure is a wall of text rather than cleanly segmented.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the full burden of describing returns, and it does so exhaustively: live counts and shares, planned work broken out, severity word, seven regional breakdowns, worst region, affected-town count, and optional daily history. It also covers the failure mode (null counts, countsReason, countsRead=false), leaving nothing an agent needs to call or interpret the tool.

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 description coverage is 100%, so both parameters (days, region) are already documented in the schema, which sets the baseline at 3. The description adds only marginal param-level meaning: it characterizes history as 'one ~06:00 AST reading per day' and confirms the region list, but adds no syntax or selection guidance beyond the schema.

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?

The description names a specific resource and scope: 'Puerto Rico's electricity grid right now, from LUMA Energy's public outage portal', with a precise breakdown of what is reported (customers out, share, planned vs unplanned, regions, worst region, affected towns). It is unmistakable what the tool returns. It does not, however, explicitly contrast itself with the adjacent get_grid_reliability sibling, so differentiation is left to the agent.

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?

Usage is implied rather than stated: the 'right now' framing and the optional 'days' history suggest when the tool fits, and the history default (0 = none, starts 2026-09-05) is explained. There is no explicit when-to-use versus get_grid_reliability or get_water_status, and no stated preconditions, so the agent must infer routing.

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

All mcp 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.

Resources

Need Help?