Skip to main content
Glama

TokenBank — tokenized real-world assets

by world.tokenbank
OverviewDiscussionsAdmin

compare_tokenized_access

Read-onlyIdempotent

For a security tokenized by more than one issuer, compare every token on it side by side — issuer, structure, KYC gates, custody, chain, and the target/area each issuer states — plus every Hyperliquid perpetual on it (fees, funding, leverage; no ownership). The right tool for "which tokenized versions of Apple exist?" and "where can I get NVIDIA on-chain, and at what cost?": the tokens and perps share a price driver and differ in almost everything else. Securities that exist on-chain only as a perp are included too. Hundreds of securities here are tokenized more than once — Apple exists as seven separate tokens; the response carries the exact counts, do not quote a figure from this description. targetArea describes who each issuer aims the product at and where; it is not an eligibility check — who may buy is set by the issuer. Omit query to list every such security.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryNoCompany name, underlying ticker or ISIN — e.g. "Apple", "AAPL", "US0378331005". Omit to list all.
offsetNoSkip this many matches before returning. Use the nextOffset from the previous answer to walk the whole set; its absence means you reached the end.
sectorNoOnly securities in this sector, e.g. "crypto" or "funds".
industryNoOnly securities in this industry, e.g. "bitcoin-miners", "semiconductors", "memory-storage".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
matchedYes
nextOffsetNoPass as offset to fetch the next page; absent when there is no more
underlyingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / industry / enum
      Previous value: -[
-  "semiconductors",
-  "semiconductor-equipment",
-  "memory-storage",
-  "software",
-  "cybersecurity",
-  "ai-cloud",
-  "ai-models",
-  "hardware",
-  "networking",
-  "electronic-components",
-  "quantum",
-  "it-services",
-  "internet-platforms",
-  "media-entertainment",
-  "telecom",
-  "ecommerce",
-  "autos-ev",
-  "retail",
-  "restaurants",
-  "consumer-staples",
-  "leisure-apparel",
-  "pharma-biotech",
-  "medtech",
-  "health-services",
-  "banks",
-  "payments",
-  "brokers-exchanges",
-  "asset-managers",
-  "insurance",
-  "financial-data",
-  "bitcoin-miners",
-  "crypto-treasury",
-  "crypto-platforms",
-  "aerospace-defense",
-  "space",
-  "machinery-electrical",
-  "transport-logistics",
-  "construction-engineering",
-  "business-services",
-  "oil-gas",
-  "utilities-power",
-  "nuclear-uranium",
-  "clean-energy",
-  "metals-mining",
-  "chemicals-materials",
-  "reits",
-  "real-estate-services",
-  "index-etf",
-  "country-etf",
-  "thematic-etf",
-  "leveraged-etf",
-  "bond-etf",
-  "commodity-etp",
-  "crypto-etp"
-]New value: +[
+  "semiconductors",
+  "semiconductor-equipment",
+  "memory-storage",
+  "software",
+  "cybersecurity",
+  "ai-cloud",
+  "ai-models",
+  "hardware",
+  "networking",
+  "electronic-components",
+  "quantum",
+  "it-services",
+  "internet-platforms",
+  "media-entertainment",
+  "telecom",
+  "ecommerce",
+  "autos-ev",
+  "retail",
+  "restaurants",
+  "consumer-staples",
+  "leisure-apparel",
+  "pharma-biotech",
+  "medtech",
+  "health-services",
+  "banks",
+  "payments",
+  "brokers-exchanges",
+  "asset-managers",
+  "insurance",
+  "financial-data",
+  "bdc-private-credit",
+  "bitcoin-miners",
+  "crypto-treasury",
+  "crypto-platforms",
+  "aerospace-defense",
+  "space",
+  "machinery-electrical",
+  "transport-logistics",
+  "construction-engineering",
+  "business-services",
+  "oil-gas",
+  "utilities-power",
+  "nuclear-uranium",
+  "clean-energy",
+  "metals-mining",
+  "chemicals-materials",
+  "reits",
+  "real-estate-services",
+  "index-etf",
+  "country-etf",
+  "thematic-etf",
+  "leveraged-etf",
+  "bond-etf",
+  "commodity-etp",
+  "crypto-etp"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / industry
      Added value: +{
+  "description": "Only securities in this industry, e.g. \"bitcoin-miners\", \"semiconductors\", \"memory-storage\".",
+  "enum": [
+    "semiconductors",
+    "semiconductor-equipment",
+    "memory-storage",
+    "software",
+    "cybersecurity",
+    "ai-cloud",
+    "ai-models",
+    "hardware",
+    "networking",
+    "electronic-components",
+    "quantum",
+    "it-services",
+    "internet-platforms",
+    "media-entertainment",
+    "telecom",
+    "ecommerce",
+    "autos-ev",
+    "retail",
+    "restaurants",
+    "consumer-staples",
+    "leisure-apparel",
+    "pharma-biotech",
+    "medtech",
+    "health-services",
+    "banks",
+    "payments",
+    "brokers-exchanges",
+    "asset-managers",
+    "insurance",
+    "financial-data",
+    "bitcoin-miners",
+    "crypto-treasury",
+    "crypto-platforms",
+    "aerospace-defense",
+    "space",
+    "machinery-electrical",
+    "transport-logistics",
+    "construction-engineering",
+    "business-services",
+    "oil-gas",
+    "utilities-power",
+    "nuclear-uranium",
+    "clean-energy",
+    "metals-mining",
+    "chemicals-materials",
+    "reits",
+    "real-estate-services",
+    "index-etf",
+    "country-etf",
+    "thematic-etf",
+    "leveraged-etf",
+    "bond-etf",
+    "commodity-etp",
+    "crypto-etp"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / sector
      Added value: +{
+  "description": "Only securities in this sector, e.g. \"crypto\" or \"funds\".",
+  "enum": [
+    "technology",
+    "communication",
+    "consumer",
+    "healthcare",
+    "financials",
+    "crypto",
+    "industrials",
+    "energy",
+    "materials",
+    "real-estate",
+    "funds"
+  ],
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • removedInput schema / properties / reach
      Removed value: -{
-  "description": "Only underlyings with at least one instrument of this reach. Use \"retail\" to find what a normal EU investor can buy.",
-  "enum": [
-    "retail",
-    "professional",
-    "closed",
-    "unknown"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / split_only
      Removed value: -{
-  "description": "Only securities where the reach DIFFERS between their tokens — i.e. the company is buyable, but not through every token on it. Default false.",
-  "type": "boolean"
-}
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish the safe, read-only, idempotent, non-open-world profile, so the description is not obligated to restate them. It adds real behavioral context: that perps carry no ownership, that targetArea is descriptive of issuer intent and not an eligibility check, and a warning not to quote figures from the description since the response holds exact counts. The only blemish is that it then quotes 'seven' tokens for Apple while warning against doing exactly that.

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 purpose is front-loaded and most sentences do work, but the prose is dense and meandering, with the self-referential count caveat occupying significant space and partially undercutting itself. It is informative without being tight.

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 and carries return values, and annotations cover the safety profile, so the description only needs to explain scope, comparative content, and response semantics. It does all of that, including what the compared fields represent and what targetArea does and does not mean.

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%, with enums and pagination semantics (offset/nextOffset, limit default) already documented in the schema, so the baseline is 3. The description's only parameter-adjacent guidance ('omit query to list every such security') repeats what the schema already states for query, and it adds no meaning for limit, offset, sector, or industry.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb (compare) and resource (a multi-issuer security's tokens and its Hyperliquid perpetuals) and enumerates what is compared: issuer, structure, KYC gates, custody, chain, target/area, fees, funding, leverage. The scope selector 'tokenized by more than one issuer' implicitly separates it from generic find/search tools, but no sibling such as compare_assets or find_tokenized_security is named, so sibling differentiation is inferred rather than stated.

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 trigger queries ('which tokenized versions of Apple exist?', 'where can I get NVIDIA on-chain, and at what cost?') and an explicit default action ('Omit query to list every such security'). There is no statement of when NOT to use it or which sibling to prefer instead, so it stops short of full routing guidance.

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

All TokenBank — tokenized real-world assets 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