Skip to main content
Glama

Alpaca

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

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

Annotations indicate readOnlyHint, openWorldHint, idempotentHint, destructiveHint false. Description adds important behavioral details: fans out to multiple sources, fallback from GDELT to GNews, soft-fail for USPTO, returns structured changes with sources and URIs. No contradiction with 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?

Description is front-loaded with example queries, but is slightly lengthy. However, every sentence provides necessary information, so it is appropriately sized for the tool's complexity.

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?

Given the tool's complexity (multiple sources, fallback logic, parameter details) and the presence of comprehensive annotations, the description covers all critical aspects. No output schema exists, but the description mentions the return structure (changes grouped by source, total_changes count, URIs).

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 has 100% description coverage, but description adds value: explains that since accepts ISO date or relative shorthand, gives examples, recommends typical monitoring values. Value parameter is clarified to accept ticker or CIK.

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 provides specific verb phrases ("What's new with X", "latest on Y") and lists the resources (SEC EDGAR, GDELT, GNews, USPTO). It clearly distinguishes from sibling tool entity_profile by stating when to use the alternative.

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?

Explicitly states when to use this tool (e.g., recent changes queries) and when to use entity_profile instead (static profile). Also gives guidance on using the since parameter with recommended values ("30d" or "1m").

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

All Alpaca 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.7/5.0
Disambiguation2/5

Several tools occupy heavily overlapping territory: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, six Polymarket tools (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread, bet_research) circle the same opportunity-finding domain, and entity_profile/recent_changes/compare_entities/validate_claim are all company-research flavored. While each pair has a stated distinction, an agent would frequently need to read deep into long descriptions to avoid misselection.

Naming Consistency3/5

All names use snake_case, so there is no style chaos, but the pattern is inconsistent: some tools are verb-first (remember, validate_claim, resolve_entity), some are noun-first (entity_profile, recent_changes, alpaca_snapshot), and many use domain prefixes (ask_pipeworx*, polymarket_*, pipeworx_*) that overlap with bare verb-noun tools. The mix is readable but does not give a predictable clue to what a tool does.

Tool Count2/5

34 tools is well above the 25+ threshold, and the count is inflated by redundant/overlapping surfaces: a beta duplicate, six overlapping Polymarket tools, and multiple meta/discovery tools (discover_tools, suggest_questions, pipeworx_trending). Only three tools actually relate to the server's stated Alpaca identity, making the scope feel sprawling rather than well-scoped.

Completeness3/5

The research/query surface is broad and covers a lot of workflows (single lookups, grounded verification, deep research, entity profiles, comparisons, change feeds). But there are notable gaps: pipeworx:// citation URIs are promised as resolvable yet no read/fetch tool exists, subscriptions cannot be updated (only created/cancelled), and the Alpaca tools are read-only with no account/order surface despite the server name. These are workaround-able but would cause friction or dead ends.

Resources