Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_lookup

Look up Yahoo Finance instruments by ticker or company name, filter by type, and paginate results to return matching symbols, names, quote types, and exchanges.

Instructions

Yahoo Finance lookup. Looks up instruments on Yahoo Finance by ticker symbol or company name, optionally filtered to one type: equity, ETF, mutual fund, index, future, currency or cryptocurrency. Page with count and start. Returns the matching instruments, each with its symbol, short name, quote type and exchange, and the total.

Input Schema

NameRequiredDescriptionDefault
typeNoInstrument type filter
countNoResult count
queryYesTicker symbol or company name
startNoResult offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / type / enum
      Added value: +[
+  "all",
+  "equity",
+  "etf",
+  "mutualfund",
+  "index",
+  "future",
+  "currency",
+  "cryptocurrency"
+]
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses the return shape (symbol, short name, quote type, exchange, total) and that count/start paginate, but says nothing about auth needs, rate limits, or result caps. It is a read-only lookup by nature, so the gaps are moderate rather than severe.

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?

Three front-loaded sentences that efficiently cover purpose, filtering, paging and return shape. The opening 'Yahoo Finance lookup.' restates the name and slightly duplicates the following clause, which is minor waste.

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?

With four parameters, one enum and no output schema, the description covers the essentials, including the return fields it would otherwise have to omit. An agent can call it correctly after reading; only the sibling-routing question is left open.

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

Parameters4/5

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

Schema coverage is 100%, giving a baseline of 3, but the description adds real meaning: it enumerates the valid type values (equity, ETF, mutual fund, index, future, currency, cryptocurrency) and reframes count/start as paging controls, whereas the schema just says 'Result count' and 'Result offset'.

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?

States a specific verb and resource ('Looks up instruments on Yahoo Finance by ticker symbol or company name') plus the scope of the type filter. It is clear what the tool does, but it does not differentiate itself from the sibling yahoo_finance_search, which an agent could easily confuse it with.

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?

The description implies usage (instrument lookup, optional type narrowing) but never states when to choose this tool over yahoo_finance_search or the yahoo_finance_ticker_quote family. The 'optionally filtered to one type' clause hints at a filtering decision without giving real when/when-not guidance.

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

Deploy Server

Other Tools