polygon-mcp

by atomcp-ai

Overview Schema Source Related Servers Discussions Admin

Python

Remote

reference_get_ticker_news

Fetch news articles for a specific ticker symbol to monitor market developments.

Instructions

Get news articles for a ticker symbol.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reference_get_ticker_news"
  }
}

Input Schema

Name	Required	Default
`sort`	No	published_utc
`limit`	No
`order`	No	desc
`symbol`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

C2.3/5.0

Behavior1/5

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

With no annotations available, the description must fully disclose behavioral traits, but it only states a simple action. It does not mention that the symbol parameter is optional, the effect of sort/order/limit, pagination behavior, or the output format, leaving significant ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is brief and front-loaded, but it is under-specified rather than appropriately sized. A single sentence without parameter context or usage notes does not earn its place for a tool with multiple parameters.

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

Completeness1/5

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

Given four parameters, no output schema, and many sibling tools, the description is severely incomplete. It lacks information on input handling, return values, filtering options, and default behaviors, making it inadequate for effective tool invocation.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention any of the four parameters (sort, limit, order, symbol). It completely fails to add meaning beyond the basic schema, leaving the agent to infer usage.

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 the tool retrieves news articles for a ticker symbol, using a specific verb ('Get') and resource ('news articles'). This distinguishes it from sibling tools focused on quotes, indicators, or reference data.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives or how it relates to other news or reference tools. The description lacks any explicit or implicit usage context beyond the basic action.

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

Deploy Server