Find stock ticker symbols by keyword using Alpha Vantage, so you can look up the right ticker for a company or asset.
Search for stock tickers on Alpha Vantage.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | ||
| keywords | Yes |
Changes observed during successful MCP inspections.
v0.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description's only added context is naming Alpha Vantage as the upstream provider; it does not mention the api_key requirement, rate limits, or what a match looks like.
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?
A single front-loaded sentence with no waste. Its problem is under-specification rather than verbosity, so it earns credit for efficiency.
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, 0% parameter coverage, and undefined behavior for the API key, an agent lacks what it needs to call this correctly. A brief note on the api_key and what is returned would close the gap.
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 description coverage is 0%, so the description must carry parameter meaning and does not. 'keywords' is only loosely implied by 'search for stock tickers', and the required api_key parameter is never mentioned at all.
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?
It names a concrete verb and resource ('Search for stock tickers'), so the basic action is clear. But it does not distinguish itself from the many stock siblings (stock_quote, stock_daily, stock_intraday), so an agent cannot tell whether this returns ticker symbols only or price data without opening the schema.
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?
No guidance on when to use this versus stock_quote or stock_daily, and no prerequisites stated. The only implied usage is 'you need a ticker symbol first', which must be inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.