Skip to main content
Glama

Tiingo

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

Schema Changelog

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

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent), the description discloses key behaviors: return payload structure (source, citation_uri, raw event payload), the mark_read side effect that affects subsequent calls, and the persistent feed nature. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, then systematically covers return payload, filtering, mark_read, and an alternative access method. Each sentence provides distinct, valuable information without redundancy or fluff.

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?

With five optional parameters and no output schema, the description covers essential return payload and core filtering, plus an external endpoint for scripts. It does not detail limit/unread_only semantics, but those are in the schema. Overall sufficient 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 already describes all five parameters (100% coverage), but the description adds context: an example type ('sec_8k'), clarifies that mark_read flags events so next call shows newer ones, and explains the since parameter with ISO timestamp. This adds meaningful usage nuance beyond the 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 clearly states a specific verb and resource: 'Pull fired events from your subscription feed.' It also describes what is returned (most recent alerts with source, citation_uri, and raw payload), which distinguishes it from sibling tools like list_subscriptions.

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

Usage Guidelines4/5

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

The description provides clear usage context: it explains filtering by type and since, mentions that polling works fine, and offers an alternative access method (GET registry.pipeworx.io/alerts.json). It does not explicitly contrast with sibling tools, but the guidance is adequate.

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

All Tiingo 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

Multiple tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded differ only in mode; several Polymarket tools (polymarket_arbitrage, polymarket_edges, polymarket_fill_risk, bet_research) target related opportunities; ai_visibility_check and scan_competitor_ai_presence overlap. The meta-tools (discover_tools, suggest_questions, pipeworx_trending) could also be confused for one another.

Naming Consistency3/5

All names are lowercase snake_case, which is consistent, but patterns vary: some are verb_noun (ask_pipeworx, resolve_entity, validate_claim), others are noun (news, crypto_prices, stock_metadata), and several use brand prefixes (pipeworx_*, polymarket_*). This mixed convention is readable but not predictable.

Tool Count2/5

35 tools is too many for a coherent, well-scoped server. The set bundles a financial data API (Tiingo) with a generic data router (ask_pipeworx), prediction-market tools, memory utilities, subscription management, and npm checks — many unrelated to the server's apparent purpose, making it feel bloated.

Completeness2/5

For a Tiingo server, core data coverage is limited to stock prices, stock metadata, crypto prices, and news — missing real-time quotes, fundamentals, forex, technical indicators, and other typical Tiingo endpoints. Conversely, the general Pipeworx platform has broad query/research/subscription coverage but that domain doesn't align with the server name, leaving significant functional gaps.

Resources