Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_ticker_info

Retrieve stock profile and quote data for a ticker symbol, including price, quote type, statistics, and summary. Provide a symbol like AAPL to get structured JSON.

Instructions

Yahoo Finance ticker info. Returns profile and quote information for a Yahoo Finance symbol such as AAPL, under modules: the profile, quote type (quoteType), price, statistics and summary modules. The symbol is the only input.

Input Schema

NameRequiredDescriptionDefault
symbolYesYahoo Finance symbol such as AAPL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the returned modules (profile, quoteType, price, statistics, summary), which is useful output context, but says nothing about read-only safety, authentication, rate limits, or error behavior. The word 'Returns' implies a read, but the description stops short of explicit behavioral coverage.

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?

The description is front-loaded and efficient, using three short sentences with no filler. The final sentence ('The symbol is the only input') is slightly redundant with the schema but useful for reinforcing the single-parameter contract.

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?

No output schema exists, so the description compensates by listing the returned modules. For a simple one-parameter read tool, this gives an agent enough to call it correctly, though the lack of sibling differentiation and usage guidance leaves a modest gap.

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 single symbol parameter is already documented with an example ('AAPL'). The description reinforces that the symbol is the only input but does not add syntax, format, or edge-case semantics beyond the schema, making the baseline 3 appropriate.

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 states a specific verb ('Returns') and resource ('profile and quote information') for a Yahoo Finance symbol, and enumerates the modules returned. It does not differentiate from sibling tools like yahoo_finance_ticker_quote or yahoo_finance_ticker_financials, so it falls short of the top score.

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 guidance on when to use this tool versus alternatives such as yahoo_finance_ticker_quote, ticker_financials, or ticker_news. The only usage-related statement is that the symbol is the sole input, which is a parameter constraint rather than an invocation decision rule.

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