Skip to main content
Glama

Signal Nodus SEC Filings

by ai.signalnodus

US energy prices and grid demand

energy_data
Read-only

Experimental (outside the core SEC path; not covered by the published accuracy eval, may change or be withdrawn): Official EIA energy figures, newest period first: electricity_price (retail cents per kWh by state and sector), fuel_price (retail gasoline and diesel dollars per gallon by region), grid_demand (hourly demand and day-ahead forecast by balancing authority). Costs $0.05 per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows to return, max 100. Default 10.
stateNoTwo-letter state code, for electricity_price.
regionNoBalancing-authority code such as CISO or ERCO, for grid_demand.
sectorNoRES, COM, IND, TRA or ALL, for electricity_price. Default RES.
seriesYesWhich EIA series to read.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds useful behavioral context: the experimental status, per-call cost, newest-period-first ordering, and the fact that data may change or be withdrawn. These go beyond annotations without contradicting them.

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?

A single, information-dense sentence packs all critical details: experimental flag, data source, series list, ordering, and cost. No filler or redundancy; every clause earns its place.

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

Completeness3/5

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

While the description covers the three series and their units, it does not clarify how the 'region' parameter applies to fuel_price (the schema only links it to grid_demand). There is no output schema, so the return format is unspecified. These gaps could lead an agent to misuse the tool or misunderstand its response.

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 100% and each parameter is described. The description adds meaningful units (cents per kWh, dollars per gallon) and clarifies what each series returns, enriching the agent's understanding beyond bare schema descriptions. However, the mapping of the 'region' parameter to fuel_price is left ambiguous, slightly reducing its value.

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?

Description clearly states it provides Official EIA energy figures across three distinct series (electricity_price, fuel_price, grid_demand), each with its own scope. This differentiates it from the many SEC/financial sibling tools, making its purpose unmistakable.

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?

Explicitly flags the tool as experimental and outside the core SEC path, warning it may change or be withdrawn. It does not name alternatives, but no sibling overlaps functionally, so the context is sufficiently clear. Cost information adds practical guidance.

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

All Signal Nodus SEC Filings toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation3/5

Most tools have clearly written descriptions, but several pairs overlap semantically: token_price/token_report, latest_filings/recent_filings, and institutional_holdings/who_holds/activist_stakes all require careful reading to pick the right one. The overlap is not severe enough for a 2, but it is still more than the occasional confusion.

Naming Consistency3/5

Names are consistently snake_case and mostly descriptive, but the set does not follow one naming convention. It mixes noun phrases (crop_data, token_report, insider_trades) with verb phrases (lookup_company, compare_filings, verify_financial_claim), and pairs like latest_filings/recent_filings create avoidable confusion.

Tool Count2/5

31 tools is too many for what is nominally an SEC Filings server, and the scope sprawls into unrelated domains such as EVM gas, tokens, prediction markets, crop data, and x402 auditing. The count does not feel earned by a coherent workflow; it feels like an uncurated bundle of endpoints.

Completeness3/5

The SEC filing workflow is reasonably covered: company lookup, search, latest/recent filings, section extraction, 8-K events, comparisons, ownership filings, and XBRL financial checks are all present. However, there is no full-filing retrieval endpoint, no deep company financial history beyond a single concept, and many non-SEC subdomains are only one-off data points, so the overall surface is still incomplete.

Resources