Skip to main content
Glama
vigneshv1cky

AlphaDesk

by vigneshv1cky

find_symbol

Resolve a company name to its exact US ticker symbol before querying any market data, or verify a ticker you were given. Returns ranked matches with symbol, name, exchange, and asset class, prioritizing exact tickers and listed exchanges.

Instructions

Find a ticker from a company's NAME, or check one you were given: {query, results: [{symbol, name, exchange, asset_class}]}, best match first.

CALL THIS BEFORE GUESSING. Every other tool here takes a ticker, and a guess that lands on the wrong listing answers confidently about the wrong company — "Robinhood" is HOOD, but an ETF named after a company often carries a symbol closer to its name than the company's own. The ranking puts an exact ticker first, then a ticker prefix, then a name prefix, then all your words present; an exchange listing outranks an over-the-counter one and a derivative is demoted.

Keyless: this is the SEC's own ticker list plus the coin pairs that can be charted, so it answers whatever the reader has connected. An empty result means no US listing matched — it does not mean the company does not exist, only that it is not in the SEC's list (a foreign line, or a private one).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does so thoroughly: it discloses the ranking algorithm, exchange-vs-OTC ordering, derivative demotion, data source (SEC ticker list plus chartable coin pairs), keyless access, and empty-result semantics.

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 dense but not bloated: purpose and result format are front-loaded, followed by routing guidance, ranking behavior, and caveats. Every sentence contributes decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple lookup tool with no output schema, the description covers return fields, ordering, data scope, and failure semantics. It also tells the agent when to use it relative to all sibling tools. The only minor omission, explicit `limit` semantics, is recoverable from the schema default.

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?

Schema coverage is 0%, so the description must compensate. It clearly defines the `name` parameter as a company name, not a ticker, and shows the query shape, but it does not explain `limit` beyond what the schema's title and default already imply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a precise verb and resource: 'Find a ticker from a company's NAME, or check one you were given.' It also shows the response shape, distinguishing this as the symbol-resolution tool among many ticker-consuming siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit routing instruction: 'CALL THIS BEFORE GUESSING,' and explains that every other tool takes a ticker. It also warns about the risk of guessing and clarifies what an empty result does and does not mean.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.