Access concise stock index quotes with the Stock Index Short Quote API. This API provides a snapshot of the current price, change, and volume for stock indexes, making it ideal for users who need a quick overview of market movements.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Index symbol (e.g., ^GSPC for S&P 500) |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the transparency burden. It discloses the output fields (current price, change, volume) and the 'concise' nature, which is useful. However, it does not mention limitations such as whether the quote is real-time/delayed, the return format, or any restrictions on symbols. This is a moderate level of disclosure for a simple read tool.
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?
The description is two sentences and avoids fluff. The first sentence is somewhat redundant with the API name, but the second adds value by listing output fields and use case. It is concise and front-loaded with the purpose.
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?
With no output schema and no annotations, the description should explain return values and context. It lists the key fields (price, change, volume) and the use case, but it does not clarify how it differs from getIndexQuote or whether the data is delayed. Given the simplicity of the tool (one required param), it is mostly complete but leaves some ambiguity compared to similar index quote tools.
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?
The input schema has 100% coverage, with the symbol parameter described as 'Index symbol (e.g., ^GSPC for S&P 500)'. The description reinforces that this is for stock indexes but does not add any additional nuance 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.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool 'Access concise stock index quotes' and specifies the output fields (price, change, volume). It is distinguished from siblings like getQuoteShort (which likely covers stocks) and getIndexQuote (which may provide full quotes) by emphasizing 'concise' and 'short', but it does not explicitly name alternative tools for full quotes.
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 description gives a clear context: 'ideal for users who need a quick overview of market movements'. This implies when to use it (quick snapshot) versus potentially heavier or more detailed quote tools. It does not provide explicit exclusions or name alternatives, but the use case is specific enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.