Skip to main content
Glama

Statec Lu

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

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint (which is true), the description discloses the mark_read side effect, noting returned events are flagged as read to affect future calls. It also explains the data source and citation_uri format, adding valuable context not present in annotations.

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?

The description is compact but information-dense, with no wasted words. It front-loads the core purpose and efficiently covers filtering, return payload, side effects, and alternative access.

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?

Given no output schema, the description fully explains return value structure (source, citation_uri, raw payload) and covers all key behaviors (filtering, mark_read, polling, external feed). Makes the tool self-sufficient.

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 covers 100% of parameters, so baseline is 3. Description adds practical semantics (e.g., 'sec_8k' as type example, ISO timestamp for since, mark_read behavior) that enrich the schema definitions.

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 uses a specific verb ('Pull') and resource ('fired events from your subscription feed'), clearly distinguishing it from siblings like 'list_subscriptions' and 'recent_changes'. It explicitly states what is returned and the feed source.

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?

Provides clear context for use ('Polls work fine') and mentions an alternative access method (public HTTP endpoint). It lacks explicit 'when not to use' exclusions, but the context is enough to guide selection.

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

All Statec Lu 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.8/5.0
Disambiguation2/5

Multiple tools have blurry boundaries: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical (beta is explicitly 'exactly' the stable version), and ai_visibility_check vs scan_competitor_ai_presence is a single-vs-batch duplicate. The six polymarket_* tools are differentiated by long descriptions, but their overlapping concerns (edges, arbitrage, fill risk, spread) would frequently misroute an agent, and discover_tools vs suggest_questions also compete.

Naming Consistency3/5

Names follow two coexisting conventions: verb_noun for actions (get_data, resolve_entity, validate_claim) and domain-prefixed families (polymarket_*, pipeworx_*, ask_pipeworx_*). Within each family the pattern is consistent, but mixing the two styles across the set, plus outliers like generate_llms_txt and bare verbs (remember, forget, recall), makes the overall scheme feel uneven though still readable.

Tool Count2/5

34 tools is well past the 'heavy' threshold and the count is not justified by the server's stated identity: a server named 'Statec Lu' (Luxembourg statistics) contains only 3 STATEC tools buried among general data-platform, prediction-market, AI-visibility, npm-scanning, and memory utilities. The sprawling, multi-domain surface would be more coherent split into separate servers.

Completeness3/5

The STATEC subset is complete (list_dataflows → dataflow_structure → get_data forms a full browse/fetch lifecycle), and the broader research surface covers entity resolution, grounded answers, comparison, claim verification, and subscription/alert/memory management. However, the overall domain is incoherent—a STATEC server missing nothing for statistics but carrying 31 unrelated tools—and there are notable gaps such as no tool to directly fetch a pipeworx:// citation URI and no execution side for the extensive Polymarket analysis tools.

Resources