Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_ticker_shares

Retrieve current share-count fields like sharesOutstanding for a Yahoo Finance symbol such as AAPL via Crawlora MCP, returning clean JSON with the symbol echoed.

Instructions

Yahoo Finance share counts. Returns the current share-count fields for a Yahoo Finance symbol such as AAPL, for example sharesOutstanding, in shares. The symbol is the only input, and the response echoes it as symbol.

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?

No annotations are provided, so the description carries the full burden. It does disclose part of the response shape (fields surfaced under a `shares` key, symbol echoed back), which is genuinely useful behavior. However, it says nothing about auth requirements, rate limits, or whether the values are point-in-time vs. historical.

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 compact sentences, front-loaded with the resource and the key output field. Slightly repetitive in restating that symbol is the only input and is echoed, but there is no padding.

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

Completeness3/5

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

With no output schema, the description must explain return values, and it only names one example field (sharesOutstanding). It is adequate for a single-parameter lookup but leaves the actual set of returned share-count fields unspecified, and it never addresses the shares_full sibling.

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 coverage is 100% and there is only one parameter, so the baseline is 3. The description confirms symbol is the sole input and that it is echoed in the response, but adds no format or syntax detail beyond the schema.

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 (current share-count fields for a Yahoo Finance symbol), with a concrete example field (sharesOutstanding). It is clear in isolation, but it never differentiates itself from the very similarly named sibling yahoo_finance_ticker_shares_full, which an agent would need to choose between.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. Given the near-identical sibling yahoo_finance_ticker_shares_full, the omission of any routing cue is a real gap.

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