searchFind securities in Equity Rank's coverage universe by ticker or company name. Returns up to 10 matches with the id to pass to fetch and the public page URL to cite. Use this first when you only have a company name.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Ticker symbol or (part of) a company name, e.g. 'AAPL' or 'Apple'. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavioral detail: returns at most 10 matches, includes the id for `fetch`, and provides the public page URL. This goes beyond the annotations without contradicting them.
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 targeted sentences with no filler. The first sentence states what the tool does, the second covers output and usage guidance. Every part earns its place and the most important information is front-loaded.
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 single-parameter read-only search tool with full schema coverage and annotations, the description is complete. It explains what is searched, the result limit, the key output fields, and how to proceed to `fetch`. Nothing essential is missing.
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 100%: the `query` parameter is fully documented with an example. The description only restates that the query can be a ticker or company name, so it does not add meaningful semantics beyond the schema. Baseline of 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 states a specific action and target resource: 'Find securities in Equity Rank's coverage universe by ticker or company name.' It also distinguishes the tool by noting it returns the id needed for `fetch` and the public page URL to cite, making its role clear relative to siblings.
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 explicit guidance: 'Use this first when you only have a company name.' This clearly tells the agent when to reach for this tool, though it does not explicitly discuss when not to use it or compare it to get_stock_valuation/list_sector_stocks.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.