Skip to main content
Glama

Polygon Io

by io.github.pipeworx-io

News

news
Read-onlyIdempotent

Massive (formerly Polygon.io) financial news: ticker-tagged US stock market headlines with publisher, article URL, image, summary, and per-ticker sentiment insights. Use for "what is the news on $TICKER" or "market-moving headlines today". Prefer over web search for equity-focused news.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNo
limitNo
orderNo
tickerNo
published_utcNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of results
statusNoAPI response status
resultsNoNews articles
next_urlNoNext page URL if available

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds context about sentiment insights and data fields without contradicting annotations. It lacks details on rate limits or pagination but does not need to repeat annotation-provided traits.

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?

Two concise sentences: the first immediately explains what the tool returns, the second gives concrete usage and a preference note. No wasted words and important context is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers main purpose and usage, and output schema presumably handles return values. However, the lack of parameter details weakens completeness for a tool with 5 parameters and no schema descriptions. It is adequate for basic ticker queries but not fully comprehensive.

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

Parameters2/5

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

Schema has 5 parameters with 0% description coverage. The description only implies 'ticker' usage via examples but does not explain sort, limit, order, or published_utc. With no param info in the description, the agent cannot confidently use all parameters, especially since the schema provides no descriptions for them.

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 it fetches financial news with ticker tags, including publisher, URL, image, summary, and sentiment. It specifies the resource (news) and distinguishes itself by focusing on equity-specific headlines, with explicit use cases and a preference over web search.

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?

Provides explicit scenarios ('what is the news on $TICKER' or 'market-moving headlines today') and advises preferring this over web search for equity news. However, it does not mention alternative tools or when not to use it, limiting exclusionary guidance.

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

All Polygon Io 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

B3.2/5.0
Disambiguation3/5

Tools like ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded have overlapping purposes (all answer questions via a universal router), with only subtle distinctions (beta version, grounded mode). Additionally, many tools like entity_profile, compare_entities, recent_changes, and resolve_entity all pull SEC/company data, and polymarket_arbitrage, polymarket_edges, polymarket_fill_risk, bet_research all relate to prediction markets, creating potential confusion. However, each tool does have a somewhat distinct purpose and detailed descriptions help differentiate them, so it's not extreme overlap.

Naming Consistency2/5

Tool names are mostly lowercase with underscores (e.g., 'ask_pipeworx', 'compare_entities', 'resolve_entity'), but there's a mix of verb-first (bulk_splits, list_subscriptions) and noun-first (data_types, get_quote) patterns. Also 'aggregates' and 'grouped_daily' both fetch bars but have different naming styles. The naming is inconsistent with no clear uniform pattern, and some names are vague like 'helpers' or 'utility-*'.

Tool Count2/5

43 tools is quite heavy for a single MCP server, exceeding the typical 15-25 range for 'too many'. While the server aggregates many different domains (Polygon stocks, Pipeworx data, Polymarket, npm, etc.), the sheer number makes it overwhelming for an agent to discover and select the right tool. Many tools are meta-tools (ask_pipeworx, discover_tools) that add complexity rather than mapping to a clear domain.

Completeness4/5

The server covers a huge range of operations: stock data (retrieve, search, details), prediction markets (arbitrage, edges, research, fill risk), entity resolution, subscriptions, memory, and meta-tools. There are some gaps like no obvious tool for modifying stock data (not expected) and the Polymarket side lacks a tool for placing actual trades or managing positions. But overall the surface is quite complete for a comprehensive data/research server.

Resources