Skip to main content
Glama

Color

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already indicate read-only, open-world, idempotent, non-destructive. The description adds significant behavioral context: parallel fan-out to multiple sources, fallback logic, and the USPTO soft-fail condition, which goes beyond annotations.

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?

The description is a single dense paragraph but well-structured with clear examples and behavioral notes. It earns its length without being verbose, though some structuring (e.g., bullet points) could improve readability.

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?

Despite no output schema, the description details the return structure (changes grouped by source, total_changes count, citation URIs). It covers edge cases (soft-fail, fallback) and provides sufficient context for agent usage.

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 descriptions for all 3 parameters. The description adds extra practical guidance, like suggesting '30d' or '1m' for since and examples of ticker/CIK formats, enhancing usability.

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's purpose: a change feed for a company over a recent window, with specific sources and example queries like 'What's new with X'. It distinguishes from sibling tool entity_profile by contrasting static vs. dynamic changes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on when to use (monitoring recent changes) and when not to (use entity_profile for static profile). Also explains fallback behavior between GDELT and GNews, and the soft-fail for USPTO due to API sunset.

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