Skip to main content
Glama

Otto Intel

by services.ottoai
OverviewDiscussionsAdmin

Otto tokenized-stock pool discovery

otto_stock_pools
Read-onlyIdempotent

Find the DEX pools a tokenized US stock or ETF is actually a member of, on Robinhood Chain, Base, BNB Chain or Solana. Returns each pool id (Uniswap v4 pool ids kept distinct from v3 pool addresses), DEX and version, which side the asset is on, the counterpart token with an evidence-backed classification (verified stock, verified stablecoin, or unclassified), reported USD liquidity and 24h volume, 24h transaction count, pool creation time, and the source coverage limits. Membership discovery only: a provider-covered observation rather than a complete census, no APR and no execution support, and the asset’s own 24h return is reported only from pools where it is the base token. Identify the asset by address when a ticker names two deployments on one chain — that spelling is refused rather than resolved to one of them. Not a pairing recommendation. Hosted access: the first eligible cached intelligence result is free; otherwise calls cost $0.001 USDC through x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stockYesNetwork-qualified tokenized-stock identity: "<network>:<TICKER>" or "<network>:<token address>", where network is robinhood, base, bsc or solana. Example: robinhood:MU. A bare ticker is rejected, and so is a ticker that names two deployments on one chain — give the token address for those.
x_paymentNoSigned x402 payment payload. Omit it to receive the machine-actionable payment challenge, then retry with the signed payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / stock / description
      Previous value: -"Network-qualified tokenized-stock identity: \"<network>:<TICKER>\" or \"<network>:<token address>\", where network is robinhood, base, bsc or solana. Example: robinhood:MU. A bare ticker is rejected, and so is a ticker that names two deployments on one chain (eight Solana tickers exist on both xStocks and Backpack) — give the token address for those."New value: +"Network-qualified tokenized-stock identity: \"<network>:<TICKER>\" or \"<network>:<token address>\", where network is robinhood, base, bsc or solana. Example: robinhood:MU. A bare ticker is rejected, and so is a ticker that names two deployments on one chain — give the token address for those."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark read-only/open-world/idempotent, and the description adds substantial behavioral context beyond them: source-coverage limits, ambiguous-ticker refusal, base-token-only return reporting, hosted-access pricing, and x402 challenge flow. No contradiction with annotations.

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 description is long and dense, but almost every sentence adds a distinct operational detail or caveat. It front-loads the core purpose before layering constraints, though a tighter structure would improve scanability.

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?

With no output schema, the description compensates by enumerating returned fields, edge cases (ambiguous tickers, base-token-only returns), coverage limits, and payment mechanics. An agent has enough information to call the tool correctly.

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%, so baseline is 3. The description adds valuable semantics around the stock parameter, especially the ticker-vs-address ambiguity rule and the x_payment challenge-and-retry behavior, exceeding what the schema alone states.

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 states a specific verb ('Find') and resource ('DEX pools a tokenized US stock or ETF is actually a member of'), and enumerates exactly what is returned. It also draws boundaries against sibling concerns such as APR and execution, making its purpose distinct.

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?

The description gives strong when-not guidance: it is membership discovery only, not a complete census, and not a pairing recommendation. It does not name a specific alternative sibling tool, but the exclusions are clear enough for an agent to avoid misuse.

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

All Otto Intel toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources