Fetch current market data for up to 50 symbols in one call: price, change, day range, volume, 52-week high/low, and market cap. Missing symbols return null.
Quotes for up to 50 symbols in one call: price, change, day range, volume, 52-week high and low, and market cap where the reader's vendors carry them. A symbol with no quote comes back null rather than missing.
| Name | Required | Description | Default |
|---|---|---|---|
| symbols | Yes |
Changes observed during successful MCP inspections.
v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It adds meaningful behavior: a 50-symbol limit, vendor-dependent market cap availability, and that missing quotes return null instead of being omitted. It does not mention rate limits or output structure, but for a read-only quote tool this is solid coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler. The core capability is front-loaded, the field list is compact, and the null-behavior caveat earns its place as a useful edge-case clarification.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool with no output schema, the description covers the main return fields, the batch limit, and a key edge case. It lacks explicit examples or format guidance for symbols, but the information provided is sufficient for an agent to call this tool correctly in most cases.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description must compensate. It clarifies that the single 'symbols' parameter can accept up to 50 symbols and explains how missing symbols are handled. It does not specify ticker formatting or the string-vs-array distinction, but it adds meaningful semantics beyond the bare schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns quote data for up to 50 symbols in one call and enumerates the exact fields included (price, change, day range, volume, 52-week high/low, market cap). This makes it easy to distinguish from sibling tools like quote or key_stats.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The batch nature ('up to 50 symbols in one call') implies when this tool should be used rather than single-symbol alternatives, but it does not explicitly name alternatives or state when not to use it. The null-behavior note adds useful usage context, but no direct comparison with sibling tools is made.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.