Find PSX ticker symbols by company name or symbol when the exact ticker is unknown; optionally filter by sector.
Search PSX ticker symbols by symbol or company name.
Use this FIRST whenever you are unsure of the exact ticker (e.g. query='Habib Bank' -> HBL). Optionally filter by exact sector name. Returns matches ranked with exact-symbol hits first.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes | ||
| sector | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, but it does disclose useful behavior: matches are ranked with exact-symbol hits first, and sector filtering is exact-match only. It omits auth/permission needs, result count behavior, and pagination, so the disclosure is partial.
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?
Three short, front-loaded sentences with zero filler; the priority instruction ('Use this FIRST') leads and the return-ordering note closes. Slightly terse but efficient.
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?
No output schema exists, and the description covers the shape of results (ranked matches) and two of three parameters, which is nearly enough for a simple lookup tool. The undocumented 'limit' parameter and absent detail on result size/truncation leave a 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 coverage is 0%, so the description must compensate. It adds real meaning for 'query' (symbol or company name, with an example) and 'sector' (must be an exact sector name), but completely ignores the 'limit' parameter and its default/behavior.
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?
States a specific verb and resource ('Search PSX ticker symbols') and the two lookup keys (symbol or company name). It doesn't explicitly name sibling tools, but the ticker-resolution role is unambiguous against get_quote/get_company_info.
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?
Explicit 'Use this FIRST whenever you are unsure of the exact ticker' with a concrete input/output example ('Habib Bank' -> HBL) and the optional sector filter condition. No when-not guidance or named alternatives, but the primary usage moment is clearly pinned down.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.