Crawlora MCP

yahoo_finance_lookup

Read-only

Look up Yahoo Finance instruments from a ticker or company query, optionally filtered by instrument type. Use yahoo_finance_search for broader finance search results.

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": {
      "Query": "<Query>"
    },
    "name": "yahoo_finance_lookup"
  }
}

Input Schema

Name	Required	Description
`Type`	No	Instrument type filter. Allowed values: all, equity, etf, mutualfund, index, future, currency, cryptocurrency. Default all.
`Count`	No	Max matches to return, default 8, max 250.
`Query`	Yes	Lookup query, a ticker symbol or company name, e.g. apple or AAPL. Required.
`Start`	No	Zero-based offset of the first result, default 0, max 10000.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the instrument-type filtering capability but nothing about rate limits, result shape, or behavior specifics beyond what annotations and the output schema convey.

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, zero waste, with the core purpose front-loaded and the sibling routing placed after. Every sentence earns its place.

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?

An output schema exists and annotations carry the safety profile, so the description needn't explain return values. It covers purpose and routing adequately; only minor behavioral depth is missing, which the structured fields largely compensate for.

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%, so the schema already documents Query, Type, Count, and Start with defaults and limits. The description only restates the instrument-type filter, adding no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb (look up) and resource (Yahoo Finance instruments) plus input form (ticker or company query). It also names the sibling it differs from, so an agent can distinguish it from yahoo_finance_search without opening either schema.

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?

Explicitly routes the agent to yahoo_finance_search for 'broader finance search results,' which implies this tool is for direct instrument lookup. It gives a clear alternative and use condition, though it doesn't spell out a hard when-not case for this tool itself.

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

All Crawlora MCP tools Inspect

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

Need Help?