Skip to main content
Glama

Ecosystems

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").

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. Description adds details about fan-out to multiple sources, fallback mechanism, and return structure. Lacks some specifics on rate limits or error handling.

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?

Well-structured: front-loaded with example queries, then explanation of behavior, sources, return format, and sibling comparison. Each sentence adds value; could be slightly more concise but overall efficient.

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?

Describes multi-source fan-out, fallback, return structure, and citation URIs. Missing pagination or result limits, but given openWorldHint, it's adequate. No output schema, so description covers key outputs sufficiently.

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 with descriptions. Description adds examples and best practices for 'since' (e.g., 'Use "30d" or "1m" for typical monitoring') and explains 'value' accepts ticker or CIK. Adds marginal but useful nuance beyond schema.

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 explicitly states it provides a 'change feed for a company in the last N days/weeks/months in ONE parallel call' and contrasts with sibling entity_profile, which is for static profiles. Example queries clearly indicate intended use.

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?

Describes when to use (e.g., 'latest on Y', 'what happened to Z') and explicitly recommends entity_profile for static profiles. Covers fallback logic (GDELT→GNews) and soft-fail for USPTO.

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

All Ecosystems 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
Disambiguation3/5

Several tools form tight clusters that are easy to confuse: ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded are near-identical in routing, and the six polymarket_* tools (edges, arbitrage, edge_tracker, fill_risk, kalshi_spread, bet_research) all operate on prediction markets with overlapping names and purposes. While each has a distinct job, an agent will need to read descriptions very carefully to pick the right one, especially when many are similar.

Naming Consistency2/5

Naming conventions are mixed throughout the set: many tools use verb_noun (ask_pipeworx, compare_entities, discover_tools, resolve_entity, validate_claim), but there are also noun_noun (polymarket_edges, entity_profile, bet_research), adjective_noun (deep_research, recent_alerts), and bare verbs (forget, recall, remember, subscribe). No consistent pattern emerges, making tool names harder to predict and remember.

Tool Count2/5

At 34 tools, this server is heavy and tries to serve many unrelated domains—data research, prediction markets, package registries, memory, subscriptions, and AI visibility. The prediction-markets cluster alone accounts for six highly specialized tools that could be consolidated. The scope feels bloated rather than focused, which will overwhelm agents exploring the toolset.

Completeness4/5

Each domain within the server has solid coverage: data lookups offer stable, beta, grounded, and deep-research variants; entity analysis has profile, compare, changes, and resolve; subscriptions support create/list/delete/alert-read; memory has set/get/list/delete. Minor gaps exist (e.g., no direct package search by keyword, no tool to update a subscription), but the major workflows are covered and there are no dead ends.

Resources