Skip to main content
Glama

FinanceQuery

Analyst Rating Consensus

get_rating_consensus
Read-onlyIdempotent

Get a stock's consensus analyst rating rollup (strong buy/buy/hold/sell/strong sell counts and a headline consensus label).

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_rating_consensus"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
symbolYesStock ticker symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety and idempotency profile is fully covered by structured data. The description contributes the shape of the payload (five rating buckets plus a label), but says nothing about data freshness, the analyst pool behind the counts, or the reporting period.

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

Conciseness5/5

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

One sentence with the payload description front-loaded and no filler. Every clause earns its place, and a parenthetical is used efficiently to enumerate the return values.

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 two-parameter read-only lookup with full schema coverage and no output schema, the description is essentially sufficient: it names the argument implicitly (a stock's rating rollup) and describes the return shape. Only minor gaps remain, such as whether counts reflect a fixed window or the latest analyst updates.

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 coverage is 100%, and both parameters ('symbol', 'fields') carry their own descriptions, so the schema does the heavy lifting. The description adds nothing about symbol format or what the comma-separated field list can contain, which is the correct baseline when the schema is fully documented.

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 pairs a specific verb ('Get') with a concrete resource ('consensus analyst rating rollup') and enumerates the returned content (strong buy/buy/hold/sell/strong sell counts plus a headline consensus label). That content distinguishes it in substance from the price-target sibling, but it never names an alternative, so the differentiation is implicit rather than explicit.

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?

Usage is implied by the description: fetch this for a ticker when you want the buy/sell rating distribution rather than price targets. There is no explicit when-to-use statement, no prerequisites, and no statement of when another tool would be the better pick.

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.