FinBrain MCP

recent_analyst_ratings

Retrieve recent analyst ratings for tracked stocks. Get ticker, institution, rating type, signal, and target price to inform investment decisions.

Instructions

Get the most recent analyst ratings across all tracked stocks. Returns rows with ticker, name, date, institution, rating_type, signal, target_price.

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": {
      "req": "<req>"
    },
    "name": "recent_analyst_ratings"
  }
}

Input Schema

Name	Required	Description	Default
`req`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. Only states return fields; no disclosure of data freshness, pagination, rate limits, or side effects. Lacks critical behavioral context.

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?

Two sentences: first for purpose, second for returned columns. Highly concise and front-loaded with essential information, no extraneous words.

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

Completeness2/5

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

Provides return columns (no output schema), but lacks parameter explanations, usage guidelines, and behavioral traits. Incomplete for a tool with nested parameters and no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. Description does not mention any parameters (market, region, limit, format) despite having 4 parameters. Fails to add meaning beyond the raw schema.

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?

Description explicitly states 'Get the most recent analyst ratings across all tracked stocks' with a clear verb and resource, and lists returned columns. It distinguishes from sibling tools like 'analyst_ratings_by_ticker' by specifying 'across all stocks'.

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?

No guidance on when to use this tool versus alternatives. Does not mention that for specific tickers the sibling 'analyst_ratings_by_ticker' should be used, nor any exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.