Skip to main content
Glama

Tiingo

by io.github.pipeworx-io

News

news
Read-onlyIdempotent

Get recent financial news articles, optionally filtered by tickers or tags. Returns title, description, URL, published date, source, and related tickers. Requires a caller-supplied Tiingo API key on the News-tier plan (Power or higher) — pass it as _apiKey. Example: news({ tickers: "aapl,msft", limit: 10, _apiKey: "your_tiingo_key" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoComma-separated tag filter (optional)
limitNoNumber of articles to return (default 10, max 100)
_apiKeyNoYour own Tiingo API key on a plan that includes the News API (Power tier or higher — tiingo.com/about/pricing). The shared Pipeworx key is on a lower plan and cannot reach this endpoint, unlike the other tools in this pack.
tickersNoComma-separated ticker filter, e.g. "aapl,msft" (optional)

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Optional — your own Tiingo API key for higher limits; omit to use the shared Pipeworx key."New value: +"Your own Tiingo API key on a plan that includes the News API (Power tier or higher — tiingo.com/about/pricing). The shared Pipeworx key is on a lower plan and cannot reach this endpoint, unlike the other tools in this pack."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 10,
+    "tickers": "aapl,msft"
+  },
+  {
+    "limit": 5,
+    "tags": "earnings"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds valuable operational context beyond those annotations: the caller must supply their own Tiingo API key on the News-tier plan, and the shared Pipeworx key will not work. It does not detail error behavior or rate limits, but the safety profile is already well covered by 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 concise and information-dense: it states the action, the returned fields, the key requirement, and includes a working example in just three sentences. Every sentence earns its place, and the most important operational caveat about the API key is clearly surfaced.

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?

There is no output schema, so the description correctly enumerates the returned fields. The input parameters are fully documented in the schema, the API key requirement and plan caveat are explicit, and the example demonstrates correct usage. An agent has everything it needs to invoke this tool correctly.

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

Parameters3/5

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

All four parameters already have full descriptions in the schema (100% coverage), so the schema carries the explanatory burden. The description's ticker/tag example reinforces the filtering semantics but adds little beyond what the schema already states; baseline 3 is appropriate.

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 states a specific verb ('Get') and a clear resource ('recent financial news articles'), and it distinguishes the scope by mentioning optional ticker/tag filters and the exact returned fields. This makes the tool's purpose immediately clear and separable from financial siblings like stock_prices or crypto_prices.

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 clearly explains how to use the tool, including an example call and the optional filter parameters. It also provides an important prerequisite, the caller-supplied Tiingo API key and plan requirement, though it does not explicitly name an alternative tool to use instead.

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