Skip to main content
Glama

fetch_news_sentiment

[Personal research only] Fetch news sentiment analysis data with sentiment scores, relevance scores, and article metadata.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tickers": "<tickers>"
    },
    "name": "fetch_news_sentiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order for results.LATEST
limitNoMaximum number of news articles to return (1-200).
topicsNoOptional news topics filter.
tickersYesComma-separated list of ticker symbols to filter news articles.
time_toNoEnd time for news articles in YYYYMMDDTHHMM format (e.g., '20240131T2359')
datatypeNoResponse data type.json
time_fromNoStart time for news articles in YYYYMMDDTHHMM format (e.g., '20240101T0000')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool returns sentiment scores, relevance scores, and article metadata, and notes a personal-research restriction, but omits operational details such as data freshness, source, rate limits, and whether results are real-time or historical.

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, front-loaded sentence with no wasted clauses. The bracketed restriction is compact and relevant, though the overall brevity leaves meaningful gaps that are captured under contextual completeness rather than conciseness.

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?

The tool has 7 parameters, no annotations, and no output schema, so the description needs to carry more context than one sentence provides. It mentions the returned data categories but does not explain the sentiment scale, relevance semantics, time-range behavior, sorting/pagination defaults, or result shape.

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 every parameter is already documented in the schema. The description adds no parameter-level detail beyond the general resource name, so the baseline of 3 is appropriate.

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 states a clear verb and resource: fetch news sentiment analysis data. It also names the core content (sentiment scores, relevance scores, article metadata). It does not need heavy sibling differentiation because no sibling tool covers news sentiment, but it also does not explicitly contrast with adjacent tools.

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?

The only usage-related cue is the bracketed note '[Personal research only]'. There is no guidance on when to use this tool versus alternatives, no exclusions, and no explanation of intended scope beyond that vague caveat.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources