Skip to main content
Glama

Bcb Br

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.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, idempotent, non-destructive), the description reveals multi-source fan-out, a soft-fail behavior for the patent API, and date parsing rules. This adds substantial operational context not visible in annotations.

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 dense but every sentence carries semantic weight: common queries, source behavior, parameter formats, return shape, and an alternative tool. It is front-loaded with the most useful usage hints and avoids filler.

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?

With no output schema, the description adequately explains the return structure (changes[] grouped by source, total_changes, pipeworx:// URIs). It covers multi-source aggregation, fallbacks, date handling, and provides an explicit alternative, making it complete for a tool of this complexity.

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%, so the baseline is 3. The description adds practical examples and recommendations: 'since' accepts ISO or relative shorthand and '30d'/'1m' is suggested for monitoring; 'value' shows ticker/CIK examples; 'type' clarifies only 'company' is supported. This goes beyond the schema's basic descriptions.

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 uses specific action verbs ('Fans out to', 'Returns') and clearly defines the resource as a change feed for a company, with concrete sources (SEC EDGAR, GDELT/GNews, USPTO). It also distinguishes itself from the sibling tool entity_profile by name and use case.

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?

The description opens with natural-language triggers ('What's new with X', 'latest on Y') and explicitly states when to use entity_profile instead for a static profile. It also communicates fallback behavior (GDELT preferred, GNews on rate limits) that informs usage decisions.

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

All Bcb Br 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

A4.4/5.0
Disambiguation5/5

Each tool has a distinct purpose; even similar tools like ask_pipeworx and ask_pipeworx_grounded are clearly differentiated by grounding behavior. Polymarket tools are separated by specific angles (arbitrage, edges, tracking, fill risk, cross-venue).

Naming Consistency5/5

All tool names use consistent snake_case with descriptive verbs (ask_, compare_, discover_, generate_, list_, recall_, etc.). No mixing of camelCase or other conventions.

Tool Count4/5

35 tools is on the higher end but justified by the breadth of functionality: Brazilian economics, Pipeworx data querying, company analysis, Polymarket betting, memory, subscriptions, etc. Each tool seems necessary, though a few could potentially be consolidated.

Completeness4/5

The tool set covers major CRUD operations and data retrieval across multiple domains. Minor gaps exist (e.g., no tool to edit subscriptions directly, but unsubscribe/resubscribe works). Overall, the surface is well-rounded for the stated purposes.

Resources