Skip to main content
Glama

FinanceQuery

Analyst Upgrades and Downgrades

get_grading_actions
Read-onlyIdempotent

Get provider-routed analyst upgrades and downgrades for a symbol.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum entries per page; omitted = curated default (25)
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default
symbolYesStock ticker symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 profile is fully covered structurally. The description adds only the 'provider-routed' framing about data provenance; it says nothing about pagination behavior, result ordering, historical depth, or what an 'action' record contains (firm, rating change, price target).

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?

A single front-loaded sentence with no filler or redundancy. It is appropriately sized for a simple filtered lookup, though the one clause it does contain ('provider-routed') spends words on a term that does not help the caller.

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?

Given the simple 4-parameter schema, full annotation coverage, and no output schema, the description is adequate but thin: an agent still cannot tell what an upgrade/downgrade record contains or how results are ordered/paged beyond the schema hints. It is complete enough to invoke correctly but not to predict 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?

Schema description coverage is 100% — limit defaults, the opaque cursor, field selection, and the symbol parameter are all documented in the schema itself. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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 a specific verb and resource — analyst upgrades and downgrades for a given symbol — which is concrete enough to distinguish it from the surrounding profile/financials/news tools. The qualifier 'provider-routed' is jargon that is neither explained nor obviously differentiating, but the core purpose is unambiguous.

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 guidance, no statement of when this is preferable to other analyst- or ratings-type data, and no prerequisites or exclusions. 'For a symbol' implies the required input but doesn't tell the agent which situations call for this tool.

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.