talon_search
Search Robinhood Chain pairs by ticker, name, or narrative keyword.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | ||
| limit | No |
Talon
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.1/5.0
Behavior2/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 of behavioral disclosure. 'Search' implies a read-only operation, but the description does not mention result shape, pagination, rate limits, or any other behavioral traits. It is not misleading, but it is minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence with no filler. The action and target resource are front-loaded, and the search dimensions are stated compactly.
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?
For a two-parameter search tool, the description plus input schema provides enough to invoke it correctly. However, with no output schema and no guidance about alternative tools, it omits what the response looks like and does not help an agent navigate the large sibling set.
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?
The description adds important meaning to the 'q' parameter by specifying that it can be a ticker, name, or narrative keyword. The 'limit' parameter is not described, but its schema constraints (default, minimum, maximum) make it self-explanatory. Overall, the description partially compensates for the 0% schema description coverage.
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 ('Search'), a specific resource ('Robinhood Chain pairs'), and the search dimensions ('ticker, name, or narrative keyword'). It does not explicitly differentiate from sibling tools like talon_scan or talon_stock, but the unique resource target makes the tool's purpose clear.
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?
No guidance is provided about when to use this tool versus the many talon_* siblings, nor are any alternatives or exclusions mentioned. Usage is only implied: use it when you need to search Robinhood Chain pairs by keyword.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.