Skip to main content
Glama

Analyst Ratings For Symbol

analyst_ratings_for_symbol
Read-onlyIdempotent

Wall Street consensus analyst rating for one US stock: the mean rating (Buy/Hold/Sell), how many analysts cover it, and the list of brokerage firms publishing recommendations on it. Use for "what do analysts think of NVDA", "who covers Apple", "consensus rating for TSLA". Sourced live from Nasdaq's public analyst endpoint.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "AAPL"
    },
    "name": "analyst_ratings_for_symbol"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesUS ticker symbol, e.g. "AAPL", "NVDA", "AMGN".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds provenance and freshness context ("Sourced live from Nasdaq's public analyst endpoint") plus a scope limitation (US stocks only), which is meaningful detail beyond the annotations. It does not discuss rate limits or failure modes, but those are secondary here.

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 core definition is front-loaded in the first sentence, followed by practical example queries and a short provenance note. Two sentences, no filler, though the three quoted example queries are slightly redundant with one another.

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?

For a single-parameter read tool with no output schema, the description usefully previews what comes back (mean rating, coverage count, firm list) and states the US-only scope. An agent has enough to call it correctly and set expectations for the response.

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?

Only one parameter and schema coverage is 100%, with the schema already giving examples of ticker format. The description's contribution is the "US stock" scoping restriction, which is useful but minimal; baseline 3 applies when the schema does the heavy lifting.

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

Purpose5/5

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

Names a specific resource (Wall Street consensus analyst rating) tied to one US stock and enumerates the exact outputs: mean rating, analyst coverage count, and list of brokerage firms. This clearly distinguishes it from sibling tools like analyst_price_targets and analyst_forward_estimates, which cover different data.

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

Usage Guidelines4/5

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

Gives concrete trigger phrases ("what do analysts think of NVDA", "who covers Apple", "consensus rating for TSLA") that map cleanly to the tool. It stops short of explicitly excluding the adjacent siblings such as analyst_price_targets or analyst_forward_estimates, so an agent must infer the boundary itself.

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.