symbol_search"Look up StockTwits ticker for [company]" / "search for symbol on StockTwits" — symbol search on StockTwits to confirm a ticker exists or find variant tickers (e.g. crypto, ETFs).
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | ||
| limit | No |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "q": "Tesla"
+ },
+ {
+ "limit": 10,
+ "q": "Bitcoin"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds domain-specific context (StockTwits) and purpose but does not disclose additional behavioral traits such as rate limits, pagination, or return format.
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 a single concise sentence with embedded examples, front-loading the key action. No extraneous information.
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?
Given the simplicity (2 params, no output schema), the description covers the primary use case but lacks details on return values and does not distinguish it from similar sibling tools like suggest_symbols.
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?
With 0% schema description coverage, the description must compensate. It implies 'q' is a company name or search term via examples and mentions variant tickers, but does not explain 'limit' or provide any parameter constraints or formatting details.
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's purpose: searching for StockTwits symbols to confirm existence or find variants. It uses specific verbs ('Look up', 'search') and resources ('StockTwits ticker', 'symbol on StockTwits'), making it unambiguous.
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 provides example queries but no explicit guidance on when to use this tool versus siblings like suggest_symbols or search_within. Users are left to infer context from the examples alone.
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.