Skip to main content
Glama

Dostuff

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?

Describes return format and side-effect of mark_read, going beyond annotations. However, annotations claim readOnlyHint=true, conflicting with mark_read's state-changing behavior. The description is accurate and transparent about this, so it is scored highly; the contradiction is flagged separately.

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?

Concise, front-loaded, and every sentence serves a purpose. No redundant information. Structured logically from purpose to specifics.

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?

For a tool with no output schema, the description adequately explains the return content. All parameters are covered, and the alternative endpoint is mentioned. The tool is simple and the description is sufficiently complete.

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 all 5 parameters with descriptions. The description adds value by explaining how mark_read affects subsequent calls, that since expects ISO format, and that polling is safe. This exceeds the baseline of 3.

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 clearly states the tool pulls fired events from subscription feeds, specifies what each event carries (source, citation_uri, raw payload), and explicitly mentions filtering by type and since. It is specific and distinguishes from sibling tools by focusing on fired events.

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 guidance on filtering, mark_read behavior, and polling suitability. Mentions an alternative endpoint for scripts/dashboards. Lacks explicit when-not-to-use instructions, but covers key usage scenarios.

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

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

The set contains near-duplicate tools (ask_pipeworx_beta explicitly 'currently matches ask_pipeworx exactly') and a dense family of six polymarket_* tools whose boundaries are subtle, plus overlapping onboarding tools in discover_tools and suggest_questions. Detailed descriptions mitigate some confusion, but several tools are difficult to tell apart without reading their full text.

Naming Consistency3/5

All names are lowercase snake_case and readable, with consistent prefix families (ask_pipeworx, polymarket_, pipeworx_), but the overall structure is mixed: bare verbs (remember, forget, subscribe), adjective+noun names (recent_alerts, recent_changes), and noun+noun domain tags (polymarket_edges, entity_profile) rather than a uniform verb_noun pattern.

Tool Count2/5

At 33 tools the set exceeds the 25-tool threshold and feels heavy, carrying an experimental duplicate of ask_pipeworx and a six-tool polymarket family that could plausibly be consolidated. The breadth reflects several unrelated domains bundled into one server rather than a focused scope.

Completeness3/5

The data-research core (ask, grounded, deep_research, profiles, comparisons, claim validation, entity resolution) and the prediction-market analysis suite are thoroughly covered, and memory plus subscription lifecycles are complete. However, the events domain the server is named for is thin (only events + metros), and the overall set lacks a single coherent purpose against which completeness can be cleanly judged.

Resources