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

Retrieve tokenized stock data to compare onchain supply by issuer and chain, wrapper prices versus reference shares, premiums, DEX liquidity, volume, 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. Without underlying, each stock lists its first 3 wrappers and 3 exchange pairs; pass underlying for all of them. Pass detail "compact" for a shorter page or "full" for the whole answer.

Input Schema

NameRequiredDescriptionDefault
topNoRows by supply (default 10, max 200).
chainNoOne chain, e.g. solana, base, bnb, robinhood, ethereum, ton, all (xStocks circulating) or cex (exchange pairs).
detailNoOptional. "compact": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). "full" or true: the whole route answer, still under the 100,000 character ceiling (the largest boards answer the ceiling note then: narrow them with symbol, limit or days instead). Omitted or false: the default first page.
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 changedv1.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / detail
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "enum": [
+        "compact",
+        "full"
+      ],
+      "type": "string"
+    }
+  ],
+  "description": "Optional. \"compact\": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). \"full\" or true: the whole route answer, still under the 100,000 character ceiling (the largest boards answer the ceiling note then: narrow them with symbol, limit or days instead). Omitted or false: the default first page."
+}
  2. Changed1 schema field changedv0.36.0
    • changedInput schema / properties / top / description
      Previous value: -"Rows by supply (default 20, max 200)."New value: +"Rows by supply (default 10, max 200)."
  3. 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"
+]
  4. 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 say readOnly/openWorld; the description adds substantial context beyond that: a 10-minute refresh cadence, the provenance rule for wrappers, the meaning of price_source values (reference / issuer_oracle / wrapper / null) and what totals.priced_by counts, and the 100,000-character ceiling behaviour with a suggested narrowing strategy. This is exactly the kind of behavioral detail annotations cannot carry.

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?

The trigger is correctly front-loaded, but the body is a dense run-on: the first sentence alone packs an issuer list, four question types and a return summary. Several clauses (the issuer enum restated inline, the detail-mode recap) repeat what the schema already says, inflating length without adding selection value. Information-dense but not disciplined.

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, yet the description specifies the return payload in usable detail: per-wrapper fields (issuer, chain, price, premium_pct, DEX liquidity, 24h volume, supply in shares and dollars, holders, status), exchange spot pairs, perpetual futures cross, and aggregate totals. An agent can answer 'what will I get back' without calling the tool first.

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 the baseline is 3 and the schema already documents top, chain, detail and issuer. The description still earns credit for clarifying the underlying parameter's cardinality effect (3 wrappers default vs. all when passed) and for restating detail modes in operational terms ('a shorter page', 'still under the 100,000 character ceiling'). Minor duplication of the schema's detail text keeps it off a 5.

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 an explicit trigger and names the precise resource (tokenized stocks / stock tokens) plus the concrete issuers it covers, then enumerates what the tool answers: onchain supply, issuer/chain dominance, premium to the real share, DEX pools and exchange pairs. No sibling tool covers this domain, and an agent can tell instantly whether a query belongs here rather than to get_tradfi_board or get_venue_markets.

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?

It gives a clear when-to-use condition (user asks about tokenized stocks, listing recognisable brand names an agent can pattern-match on) and a scoping rule: 'Without underlying, each stock lists its first 3 wrappers and 3 exchange pairs; pass underlying for all of them.' It also states a negative constraint ('Wrappers come from issuer sources only, never from a name search'), which pre-empts a wrong expectation. What it lacks is explicit routing away from any other tool, though no sibling is a real alternative.

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