Skip to main content
Glama

StocksScores

Score one stock

get_stock_analysis
Read-only

The 0-100 composite for a symbol with its technical, fundamental and news pillars, the per-timeframe technical scores, every sub-score, and the current quote. Computed live and cached for two hours — the same numbers the analysis page draws.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_stock_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker, e.g. AAPL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description discloses that the score is computed live and cached for two hours, which tells the agent about freshness and staleness of results — real behavioral context the annotations do not carry. It also frames the output as identical to the analysis page, aiding trust. It says nothing about failure modes for unknown or delisted tickers.

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?

Two sentences, front-loaded with what the caller receives, then a short behavioral note on caching. Little waste; the closing clause about the analysis page is mildly decorative but earns some trust value.

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

Completeness4/5

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

With no output schema, the description correctly discharges the return-value burden by enumerating the composite, pillars, timeframe scores, sub-scores and quote. Freshness is covered. What is missing is any hint about valid-symbol behavior or what the agent sees on an unscored symbol.

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?

There is exactly one parameter and the schema documents it at 100% coverage with an example (AAPL), so the schema carries the burden. The description adds that the symbol resolves to a single scored entity but gives no format detail (exchange suffixes, casing) beyond the schema's example.

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 concrete resource precisely: a 0-100 composite for one symbol plus its technical/fundamental/news pillars, per-timeframe technical scores, sub-scores and current quote. That is far more specific than the title 'Score one stock'. It does not explicitly differentiate itself from get_score_history or top_scores, so it stops 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 Guidelines2/5

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

There is no when-to-use statement and no named alternative — nothing tells the agent to prefer get_score_history for time series or screen_stocks for multi-symbol work. The only implicit signal is the singular 'for a symbol', which is a weak scope hint rather than guidance.

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.