Skip to main content
Glama

Entso E

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotent, read-only, non-destructive behavior. The description adds context about return fields (source, citation_uri, payload), the persistence of read flags via mark_read, and that polling is safe. This goes beyond annotations without contradiction.

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?

Three sentences deliver purpose, key parameters, and an alternative access method without redundancy. The structure is front-loaded with the main action. Minor extra detail about the GET endpoint could be omitted but does not detract.

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?

Given the absence of an output schema, the description covers return fields, filtering, and side effects (mark_read). It mentions polling but not pagination or limit behavior beyond schema. Overall sufficient for a tool with 5 optional parameters and rich annotations.

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%, so baseline is 3. The description adds value by explaining filter usage ('e.g. sec_8k'), clarifying that 'since' expects an ISO timestamp, and describing the effect of 'mark_read' on subsequent calls. This enriches schema descriptions.

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 clearly states the tool pulls fired events from a subscription feed, using specific verbs like 'Pull' and resource 'subscription feed'. However, it does not explicitly differentiate from sibling tools such as 'subscribe' or 'list_subscriptions', leaving some ambiguity.

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?

The description mentions polling works fine and provides filtering examples (type, since), implying typical usage. But it lacks explicit guidance on when not to use this tool or when to choose alternatives like 'list_subscriptions' or the GET endpoint. No conditions or limitations are stated.

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

All Entso E 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

B3.3/5.0
Disambiguation2/5

The ENTSO-E energy tools are clearly distinct, but the Pipeworx half contains overlapping query modes: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, and ask_pipeworx/ask_pipeworx_grounded/deep_research/validate_claim all route natural-language questions to the same underlying catalog. The Polymarket tools also blur edge detection, arbitrage, fill-risk, and persistence tracking, so an agent can easily select the wrong one.

Naming Consistency2/5

The five ENTSO-E tools use a clean snake_case noun pattern, but the rest mix brand verbs (ask_pipeworx, bet_research), bare memory verbs (remember, recall, forget), and polymorphic prefixes (polymarket_*), with inconsistent suffixes like beta, grounded, and kalshi_spread. There is no server-wide predictable naming convention.

Tool Count2/5

36 tools is too many for the apparent scope, and the server name promises ENTSO-E while only 5 of 36 tools serve that domain. Even viewed as a general data utility, the count is heavy and includes duplicate query modes, though individual clusters do have some purpose.

Completeness3/5

For an ENTSO-E server, the five energy tools cover the basics (generation, load, price, flow, capacity) but omit common datasets like generation forecasts, balancing/imbalance prices, and outages. The unrelated Pipeworx tools add broad research, memory, and subscription coverage, but the overall surface feels like a general-purpose assistant with an energy add-on rather than a complete energy domain.

Resources