Skip to main content
Glama

Color

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?

Goes beyond annotations by detailing return structure (source, citation_uri, payload), filtering options, and the side effect of mark_read. All behavior disclosed 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences plus a brief note, front-loaded with purpose. Every sentence adds unique value—no redundancy or fluff.

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 read-only tool with 5 optional parameters and no output schema, the description covers return fields, filtering, marking read, and alternative access. Completely 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 all parameters (100% coverage). Description adds value with examples (e.g., 'sec_8k') and clarifies behavior of mark_read and since. Exceeds baseline.

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 pulls fired events from the subscription feed, with specific verbs and resource. It distinguishes itself from sibling tools like list_subscriptions and subscribe by focusing on retrieving alert 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 usage context by mentioning polling works fine and an alternative HTTP endpoint for scripts/dashboards. Could be more explicit about when not to use, but overall clear.

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

All Color 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
Disambiguation2/5

Several tools are near-identical: ask_pipeworx and ask_pipeworx_beta are explicitly the same right now, and the three ask_pipeworx variants plus deep_research all route the same underlying catalog. The six polymarket_* tools also have heavily overlapping purposes, requiring deep reading to choose correctly. Most other tools are distinguishable, but these clusters create real misselection risk.

Naming Consistency3/5

The set is uniformly snake_case and mostly descriptive, with consistent micro-families like remember/recall/forget and polymarket_*. However, there is no single convention across the server: verb_noun names (ask_pipeworx, list_subscriptions) mix with noun-first names (entity_profile, bet_research, nearest_color), and the Pipeworx brand is used as both prefix and suffix. Readable but inconsistent.

Tool Count2/5

At 34 tools, the surface is far larger than a typical well-scoped server, and the count is especially unjustified for a server named 'Color' where only three tools relate to that name. The breadth stems from bolting a full data-research platform, prediction-market suite, memory store, and subscription system onto what appears to be a simple utility. Too heavy.

Completeness4/5

For the dominant Pipeworx research domain, the set is unusually thorough: query, grounded verification, deep research, entity resolution, comparisons, claim validation, change feeds, subscriptions, alerts, memory, and discovery are all present. Minor gaps exist (e.g., no direct account management tool, and color coverage only includes convert/contrast/nearest with no palette generation), but these are workaround-able. Completeness is strong for the real domain, if mismatched with the server name.

Resources