massive-mcp

by danielbres

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_news

Fetch news articles about stocks. Optionally filter by ticker symbol, date range, and set pagination.

Instructions

Recent news articles, optionally filtered by ticker.

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": "get_news"
  }
}

Input Schema

Name	Required	Description
`ticker`	No	Optional symbol filter (e.g. "AAPL").
`published_utc_gte`	No	Inclusive lower bound on publish time ("YYYY-MM-DD" or RFC3339).
`published_utc_lte`	No	Inclusive upper bound.
`limit`	No	Max articles. Default 10.
`cursor`	No	Pagination cursor.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 8, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It mentions 'recent' without defining the time range, omits return structure (despite an output schema existing), and lacks details on pagination, rate limits, or data sources.

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?

The description is a single concise sentence, front-loading the core action. While very short, it avoids unnecessary words, but could include more context without becoming bloated.

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

Completeness2/5

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

Given five parameters and an output schema, the description is too sparse. It does not explain what 'recent' means, how results are ordered, or what fields are returned, leaving agents with insufficient context.

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?

Schema description coverage is 100%, so baseline is 3. The description adds minimal value beyond the schema, only reinforcing the ticker filter. It does not mention other parameters like date bounds or pagination.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns recent news articles with optional ticker filtering, which is a specific verb+resource. However, it does not differentiate from siblings like 'get_ticker_events' or 'get_snapshot', though the tool's function is distinct enough.

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 on when to use this tool versus alternatives. The description provides no context about when to choose this over other news or data tools, nor any prerequisites or excluded scenarios.

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