Skip to main content
Glama

Find the official Stock Token

find_stock_token
Read-onlyIdempotent

Resolve a stock ticker (for example NVDA) to the official Robinhood Chain Stock Token contract address, with a count of the known lookalike contracts using that ticker.

Call this first, every time, before acting on a ticker a user typed: a ticker is not an address, and impostor contracts reuse real tickers. Use only the address this returns; a lookalike is a different contract with the same name.

lookalikes is how many impostor contracts Zorvu's scan has seen for this ticker, with the time of that scan in lookalikes_at. A lookalike's liq_peak is the highest liquidity ever seen for it, not what it holds now. An unknown ticker comes back as not an official Stock Token rather than guessed at. These are registry and scan measurements, not advice. Zorvu is not affiliated with Robinhood Markets, Inc. or its affiliates.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "find_stock_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker, for example NVDA.

Output Schema

NameRequiredDescriptionDefault
nameNo
pageNo
statusNo
symbolYes
addressYes
disclaimerYes
lookalikesYes
multiplierNo
lookalikes_atYes
lookalike_examplesNo
registry_synced_atYes
official_stock_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly, idempotent, and openWorld annotations, it discloses important behavior: unknown tickers return as not an official Stock Token rather than a guess, lookalikes are counted separately, lookalikes_at records scan time, and liq_peak is historical peak liquidity rather than current liquidity. It also notes that results are registry and scan measurements, not advice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and first-step usage are front-loaded, followed by useful caveats about lookalikes and unknown tickers. It is somewhat long and repeats the impostor-contract concept, and the affiliation disclaimer adds little to invocation guidance.

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 one-parameter, read-only resolver with annotations and an output schema, the description covers purpose, first-step usage, edge cases, return-field semantics, and the non-advice framing. Nothing an agent needs in order to call it correctly is missing.

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 single symbol parameter is fully documented in the schema with the same NVDA example. The description adds that the ticker is user-typed and not an address, but it provides no syntax or format detail beyond what the schema already supplies.

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?

States a specific verb and resource: resolving a stock ticker to the official Stock Token contract address. It also makes its first-step role explicit by saying to call it before acting on a user-typed ticker, which separates it from downstream token and transaction tools.

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

Usage Guidelines4/5

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

Explicitly says to call this first every time before acting on a typed ticker and to use only the returned address. However, it does not name alternatives such as check_token or state when-not to use this resolver.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources