Skip to main content
Glama

Stock Token sell depth

stock_sell_depth
Read-onlyIdempotent

How much of an official Robinhood Chain Stock Token could actually be sold on-chain right now, and at what price against the reference price. Returns what the pools filled at $1,000, $10,000 and $100,000, and the largest size they took within 2% and within 5% of the reference price. Give a ticker or an address; a ticker resolves only to the official token, never to a lookalike.

Call this before sizing a sell, a liquidation or a position you intend to unwind on-chain, and when deciding what a Stock Token is worth as collateral or margin. Impact figures are negative percentages: -0.82 means a $10,000 sell filled 0.82% below the reference price.

Every figure carries the time it was measured and its age in seconds. Readings older than 30 minutes, and max-size searches older than 2 hours, are reported as no reading rather than as a number: treat a missing figure as unknown, never as zero or as deep. capped: true means the search stopped at its ceiling, so the real size is at least that large. These are measurements of past fills, not a quote, not a promise of what you could sell now, and not advice. Zorvu does not total liquidity across tokens: a pool pairing two Stock Tokens counts toward both.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stock_sell_depth"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoTicker, for example NVDA. Resolves only to the official Stock Token, never to a lookalike.
addressNoContract address of an official Stock Token.

Output Schema

NameRequiredDescriptionDefault
noteYes
ladderYes
symbolYes
addressYes
read_atYes
max_sizeYes
freshnessYes
checked_atYes
disclaimerYes
api_versionYes
hops_at_100kYes
route_fee_bpsYes
reference_priceYes
reference_sourceYes
reading_age_secondsYes
official_stock_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark it read-only, idempotent, open-world and non-destructive, and the description adds substantial context beyond them: staleness thresholds (30 minutes for readings, 2 hours for max-size searches) reported as no reading, 'treat missing as unknown, never zero or deep', `capped: true` meaning a floor, and negative-percentage impact sign convention. It also discloses that liquidity is not netted across tokens, which an agent could not infer from anything structured.

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?

Front-loaded with what it returns, then usage, then caveats — a sensible ordering. It is dense but nearly every sentence carries non-redundant information (sign convention, staleness, capped flag, disclaimer); only the closing 'not advice' and the token-netting note feel slightly appended.

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?

An output schema exists, so return-value explanation is not required, and the description nonetheless covers freshness semantics, floor-vs-exact handling, and sign conventions that the schema alone would not convey. For a two-optional-parameter read tool with annotations, nothing an agent needs to call or interpret it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents both fields, so the baseline is 3; the description adds real meaning by stating that exactly one of ticker or address is supplied and that a ticker resolves only to the official token, never a lookalike. That resolution rule matters for correctness and is not fully implied by the schema patterns.

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 — how much of a Stock Token can be sold on-chain right now and at what price versus the reference — and enumerates the exact outputs ($1,000/$10,000/$100,000 fills, largest size within 2% and 5%). This is clearly distinct from discovery or precheck siblings such as find_stock_token and precheck_transaction.

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?

Gives concrete triggers: call before sizing a sell, a liquidation, unwinding a position on-chain, or when valuing a Stock Token as collateral or margin. It does not name an alternative tool or say when not to use it, but the 'not a quote, not a promise' framing sets a clear boundary on reliance.

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