Skip to main content
Glama

Bts

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

A5/5.0
Behavior5/5

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

Behavioral details are well-articulated: read-only, idempotent, non-destructive (consistent with annotations), plus source-specific behaviors like PatentsView soft-fail and structured return format with citation URIs. No 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?

The description is front-loaded with example queries and is efficiently structured. Every sentence earns its place, covering purpose, inputs, behavior, and alternatives without redundancy.

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 adequately explains the return format (changes[] grouped by source, total_changes count, pipeworx:// URIs). It covers all essential aspects for correct tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the description adds meaningful usage context: examples for 'since' (ISO date vs relative), typical value ('30d'), and explanation for 'value' (ticker or CIK). It also notes 'type' is limited to 'company'.

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 that the tool provides a change feed for a company over a time window, fanning out to SEC EDGAR, GDELT/GNews, and USPTO. Example queries and differentiation from entity_profile make purpose clear.

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 provides explicit when-to-use guidance (e.g., 'Use entity_profile instead when you want the static profile') and explains source fallback behavior (GDELT preferred, GNews on rate-limit). It also specifies input formats and supported entity types.

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

All Bts 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/5.0
Disambiguation4/5

Most tools have distinct purposes with clear descriptions, but the multiple ask_pipeworx variants and several Polymarket tools could cause initial confusion. An agent reading carefully can differentiate them, but the similarity in themes requires attention.

Naming Consistency3/5

Names use a mix of conventions: verb_noun (ask_pipeworx, compare_entities), noun_noun (entity_profile, dataset_columns), and single verbs (remember, forget). While some subgroups have internal consistency (e.g., polymarket_*), there is no overall predictable pattern.

Tool Count2/5

With 34 tools, the count exceeds the 'too many' threshold of 25. While the server is comprehensive, the large number of highly specific tools (especially for prediction markets) feels overwhelming and could confuse agents.

Completeness4/5

The tool set covers a wide range of capabilities: data querying, entity resolution, company analysis, prediction markets, memory, subscriptions, and validation. Minor gaps exist (e.g., no data writing tools), but for the read-heavy analytical purpose, it is nearly complete.

Resources