Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

yahoo_finance_ticker_actions

Read-only

Fetch dividend, split, and capital-gain event records for one Yahoo Finance symbol. Use yahoo_finance_ticker_dividends, yahoo_finance_ticker_splits, or yahoo_finance_ticker_capital_gains when you need just one action type; use yahoo_finance_ticker_history for adjusted price history.

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": "yahoo_finance_ticker_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesYahoo Finance symbol such as AAPL.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The tool carries readOnlyHint and openWorldHint annotations, so the safety and open-world nature are already declared. The description adds the aggregate scope (all three event types) but says nothing about return format, pagination, or data range, which the output schema may cover. With annotations and output schema present, the bar is lower, and the description does add the aggregation 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?

A single dense sentence front-loads what the tool does and follows with precise routing alternatives. Zero waste, ideal structure.

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?

The tool is a simple one-parameter read with annotations and an output schema, so the description is largely complete. It could mention any filtering or date-range options if available, but for a single-symbol event fetch it covers the essentials.

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?

The input schema fully documents the single 'symbol' parameter with a clear example, so the baseline is 3. The description restates that it operates on one Yahoo Finance symbol but adds no syntax or format detail the schema lacks.

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?

The description uses a specific verb ('Fetch') and names the exact resource ('dividend, split, and capital-gain event records') for a single symbol. It clearly distinguishes itself from the sibling tools that return just one action type.

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

Usage Guidelines5/5

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

It explicitly names three alternative tools for single action types and another for adjusted price history, telling the agent exactly when to prefer them. This is textbook routing guidance.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources