Skip to main content
Glama

Sentiment-scored news

news
Read-only

Sentiment-scored news (GET https://app.deepvalues.ai/api/v1/news/{ticker}, e.g. https://app.deepvalues.ai/api/v1/news/AAPL — 0.001 credits per call ($0.005 when paid per call over x402); works with no credentials up to 25 call(s)/day per address) Missing data? Call request_data.

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": {
      "ticker": "<ticker>"
    },
    "name": "news"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNo
tickerYesThe real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}.
sentimentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / ticker / description
      Added value: +"The real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}."
    • addedInput schema / properties / ticker / examples
      Added value: +[
      +  "AAPL"
      +]
  2. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover read-only and open-world traits, and the description adds genuinely useful operational context: per-call credit cost, x402 pricing, and a 25 calls/day unauthenticated allowance per address. What it omits is how many articles are returned, over what default time window, or whether sentiment scores are included in the payload.

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

Conciseness3/5

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

It is a single front-loaded sentence, but a large share of it is pricing and endpoint boilerplate rather than task-relevant semantics. The fallback hint is placed well at the end.

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?

Auth, cost, and a fallback path are covered, which matters for a paid open-world read. However, with no output schema and two of three parameters unexplained, an agent still cannot predict what the response looks like or how filtering changes it.

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?

With schema coverage at only 33%, the description needs to carry parameter meaning, but it explains only the ticker (via the path example). The `since` date filter and the `sentiment` enum (bullish/bearish/neutral) are never clarified as to how they filter results.

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 names the resource ('Sentiment-scored news') and pins it to a concrete endpoint with a worked example path (/news/AAPL), so an agent knows it retrieves news for a ticker. It does not differentiate from the sibling `sentiment` or `brief` tools, so it falls short of a 5.

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

Usage Guidelines3/5

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

The only routing guidance is the fallback 'Missing data? Call `request_data`', which implies usage when the news lookup returns nothing. There is no statement of when to prefer this over `sentiment` or `brief`, or when to narrow by the `since`/`sentiment` filters.

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