Skip to main content
Glama

Value-investor sentiment rollup (not WSB noise)

sentiment
Read-only

Value-investor sentiment rollup (not WSB noise) (GET https://app.deepvalues.ai/api/v1/sentiment/{ticker}, e.g. https://app.deepvalues.ai/api/v1/sentiment/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": "sentiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNocombined
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}.
windowNo7d

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.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description gets credit for adding cost per call (0.001 credits, $0.005 via x402) and the no-credential quota (25 calls/day per address) — genuinely useful operational context. It does not describe what a rollup returns (scores? volume? per-source breakdown), which matters for interpreting results.

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?

The title and the tool's core scope are front-loaded, and no sentence is pure filler — pricing, auth, endpoint, and escalation all carry weight. But the parenthetical packs endpoint, cost, quota, and remedy into one run-on string, making it harder to scan than a short structured sentence list would be.

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 model, rate limit, cost, and endpoint are all covered, which is strong for an open-world GET tool with no output schema. What is missing is the meaning of the two enum parameters and any sense of what the returned sentiment rollup contains, leaving the agent able to call it but not to choose parameters knowledgeably.

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 coverage is only 33%: the ticker has a description, but `source` (reddit/stocktwits/combined) and `window` (24h/7d/30d) have no schema descriptions at all. The description does not explain what these enums mean, how 'combined' aggregates, or how the window affects the rollup, so the two enum parameters remain semantically opaque.

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?

Names a specific resource (sentiment rollup) with an explicit scoping qualifier ('value-investor... not WSB noise') that separates it from general social chatter, and pins it to a concrete endpoint (/sentiment/{ticker}). It is a noun phrase rather than a verb, so an agent must infer the operation is a read, but the resource and audience scope are unambiguous.

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 'not WSB noise' qualifier implies this is the right tool for value-oriented sentiment vs. retail-meme sentiment, and 'Missing data? Call `request_data`' gives an explicit escalation path. However, it never states when to prefer this over siblings like news, brief, or research, nor does it set exclusions beyond the WSB aside.

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