Skip to main content
Glama
Sign In

energyai

by com.energyaisolution
OverviewDiscussionsAdmin

energy_track_record

Energy Odds public track record, free forever: per series counts, Brier score, CRPS, calibration bins and the same scores for two simple baselines, plus the go-paid gate result and its reasons. [always free — no API key required]

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "energy_track_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoOptional existing EnergyAI key for hosts that cannot change Authorization headers. Use it to retain account identity for discovery and get_builder_upgrade_link after a trial. Removed before tool execution and persistence. Omit when the Bearer header is attached; never show the key to the user.
seriesNoOptional: one series. Omit for all three.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the access model well ('always free — no API key required', 'public track record, free forever'), which is genuinely useful, but it says nothing about whether results are paginated, how large the payload is, or explicitly that it is a read-only, non-mutating endpoint.

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?

One front-loaded sentence that packs the return contents and the free/no-key caveat without filler. The bracketed access note is separable but short and earns its place as a cost/auth signal.

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?

There is no output schema, and the description compensates by enumerating the returned metrics (Brier, CRPS, calibration bins, baseline scores, gate result with reasons). For a no-required-parameter read tool, that is sufficient for an agent to know what it will get back.

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 (apiKey, series) are already documented, including the enum values, and the baseline is 3. The description's phrase 'per series' hints at the series filter but adds no new meaning about the apiKey parameter or the behavior of omitting series.

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 ('Energy Odds public track record') and enumerates exactly what it contains: per-series counts, Brier score, CRPS, calibration bins, baseline scores, and the go-paid gate result. That is enough to distinguish it from siblings like energy_forecast or verify_forecast, though it uses no explicit verb (retrieve/get).

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 only implied — an agent can infer this is the tool for auditing published forecast accuracy, but the description never states when to use it versus energy_forecast or verify_forecast, nor any exclusions. The 'always free' note nudges toward exploratory/lookup use but is not real when-to-use guidance.

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

All energyai 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