Skip to main content
Glama

Cactus

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
Behavior1/5

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

The description directly contradicts the annotations. Annotations declare readOnlyHint=true and idempotentHint=true, but the description says 'Set mark_read:true to flag returned events read so the next call only shows newer ones,' implying a state-changing side effect. This is a clear contradiction, grounding the score at 1 per the rubric.

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 three sentences, ~90 words, and front-loaded with purpose, then return format, filtering, mark_read semantics, and an alternative endpoint. Every sentence earns its place with no redundancy or fluff.

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 5 optional parameters and no output schema, the description covers essential return payload details (source, citation_uri, raw payload), filter mechanics, mark_read side effects, and even an HTTP alternative. It omits minor edge cases like pagination behavior or rate limits, but these are adequately covered by the schema and 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% with good descriptions for all 5 parameters. The description goes beyond the schema by giving a concrete type example ('sec_8k') and explaining the behavioral consequence of mark_read on subsequent calls. This adds genuine semantic value, pushing it above the baseline 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 opens with a specific verb+resource: 'Pull fired events from your subscription feed.' It clearly distinguishes this tool from siblings like list_subscriptions by focusing on retrieving fired alerts rather than managing subscriptions. It also specifies what the returned alerts contain, solidifying purpose.

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?

The description gives clear context for use: filtering by type/since and marking read, plus notes that polling works fine. It names an alternative (GET registry.pipeworx.io/alerts.json) for scripts/dashboards, which implicitly contrasts with this tool's interactive use. It lacks explicit exclusions, but the context is strong enough for a 4.

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

All Cactus 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.9/5.0
Disambiguation3/5

Most tools have clearly differentiated roles, but several pairs blur boundaries: ask_pipeworx and ask_pipeworx_beta are currently functionally identical, and identify vs resolve both wrap the same NCI CACTUS service. The detailed descriptions rescue most selections, but an agent could easily mispick between the research and chemical lookup options.

Naming Consistency3/5

Names are mostly snake_case and readable, but conventions are mixed: some are verb-first (ask_pipeworx, validate_claim, search_within) while many are noun-first or domain-prefixed (entity_profile, polymarket_edges, recent_changes, pipeworx_trending). There is no single predictable pattern for a new tool's name, though subfamilies (polymarket_*, ask_pipeworx_*) are internally consistent.

Tool Count3/5

At 33 tools, this is well above the typical well-scoped range and carries real selection overhead. The unusually broad purpose—a data router plus prediction-market analysis, memory, subscriptions, and several standalone utilities—partially justifies the count, but it still feels heavy and could be consolidated.

Completeness4/5

For its varied subdomains, coverage is strong: memory has remember/recall/forget, subscriptions have subscribe/unsubscribe/list/recent_alerts, and prediction markets span research, edge scanning, arbitrage, fill-risk, and edge telemetry. Minor gaps exist—such as no direct tool to fetch a specific citation URI by identifier, and the redundant stable/beta router pair—but there are no obvious dead ends.

Resources