Skip to main content
Glama
bykarantelicom

bykaranteli-mcp

by bykarantelicom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Tokenized stocks onchain: supply, premium to the real share, DEX pools and exchange pairs

get_tokenized_stocks
Read-only

Compare tokenized stock wrappers by issuer, chain, price premium, DEX liquidity, supply, holders, and exchange pairs.

Instructions

Call this when the user asks about tokenized stocks or stock tokens (xStocks, Ondo, Robinhood stock tokens, Coinbase tokenized stocks on Base, Binance bStocks, Backpack, Gate gStocks, Reality, Superstate, Figure, Dinari dShares, Securitize): how much of a stock exists onchain, which issuer or chain holds the most, whether a wrapper trades above or below the real share, which DEX pools or exchanges trade it. Returns the board ByKaranteli refreshes every 10 minutes: per underlying the reference share price and its session, each wrapper (issuer, chain, price, premium_pct against a fresh reference, DEX liquidity and 24h volume from admitted pools, supply in shares and dollars, holders, status), tokenized spot pairs on the exchanges the board lists, the perpetual futures cross, and totals (supply by issuer and chain, DEX volume, median premium). Each wrapper's price_source names the price that valued its supply dollars (reference: the share's reference price; issuer_oracle: the issuer's own price for the token; wrapper: its own pool or exchange price; null: no dollars), and totals.priced_by counts the counted wrappers per level, unpriced included. Wrappers come from issuer sources only, never from a name search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoRows by supply (default 20, max 200).
chainNoOne chain, e.g. solana, base, bnb, robinhood, ethereum, ton, all (xStocks circulating) or cex (exchange pairs).
issuerNoOne issuer: xstocks, robinhood, coinbase, bstocks, ondo, backpack, gstocks, reality, superstate, figure, dinari or securitize; omit for every issuer.
underlyingNoStock ticker, e.g. TSLA; omit for the whole board.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.31.0
    • changedInput schema / properties / issuer / description
      Previous value: -"One issuer; omit for every issuer."New value: +"One issuer: xstocks, robinhood, coinbase, bstocks, ondo, backpack, gstocks, reality, superstate, figure, dinari or securitize; omit for every issuer."
    • changedInput schema / properties / issuer / enum
      Previous value: -[
-  "xstocks",
-  "robinhood",
-  "coinbase",
-  "bstocks",
-  "ondo",
-  "backpack",
-  "gstocks"
-]New value: +[
+  "xstocks",
+  "robinhood",
+  "coinbase",
+  "bstocks",
+  "ondo",
+  "backpack",
+  "gstocks",
+  "reality",
+  "superstate",
+  "figure",
+  "dinari",
+  "securitize"
+]
  2. Addedv0.30.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only give readOnlyHint and openWorldHint, but the description adds substantial behavioral context: the board refreshes every 10 minutes, the exact composition of each row (reference share price and session, per-wrapper premium_pct vs a fresh reference, DEX liquidity and 24h volume, supply in shares and dollars, holders, status), and the meaning of price_source and totals.priced_by. This is well beyond what the annotations convey.

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

Conciseness3/5

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

Strongly front-loaded with the trigger condition, but delivered as one very dense run-on paragraph. The long parenthetical issuer list largely duplicates the schema's issuer enum, and the price_source/totals detail is packed tightly without structure, so not every clause earns its place independently.

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?

There is no output schema, so the description must carry the return-value burden, and it does: it describes the per-underlying layout, wrapper fields, exchange pairs, perp cross, totals, and the price_source taxonomy. An agent can interpret the response without additional documentation.

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 description coverage is 100%, so top, chain, issuer, and underlying are already documented with defaults, ranges, patterns, and the issuer enum. The description reinforces the chain/issuer vocabulary but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 (return the tokenized-stocks board) and enumerates the exact concept space (xStocks, Ondo, Robinhood, bStocks, etc.). No sibling tool in the list covers tokenized equities, so the agent can route to it unambiguously from the name plus the opening clause.

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?

Front-loads an explicit trigger: 'Call this when the user asks about tokenized stocks or stock tokens' followed by the concrete issuer/protocol vocabulary an agent would encounter. It also states an exclusion ('Wrappers come from issuer sources only, never from a name search'), so misuse is guarded against.

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

Deploy Server

Other Tools