Skip to main content
Glama

TokenBank — tokenized real-world assets

Compare tokens on one security

compare_tokenized_access
Read-onlyIdempotent

For a security tokenized by more than one issuer, every token on it side by side (issuer, structure, KYC gates, custody, chain and each issuer's stated target/area), plus every Hyperliquid perpetual on it (fees, funding, leverage; no ownership). Also covers securities that exist on-chain only as a perpetual. Exact counts are in the response. targetArea describes the issuer's stated audience, not eligibility. Without query it lists every such security; sector and industry filters are available.

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": "compare_tokenized_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryNoCompany name, underlying ticker or ISIN — e.g. "Apple", "AAPL", "US0378331005". Omit to list all.
offsetNoNumber of matches to skip; the nextOffset of a previous answer continues from there (absent at 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

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 / offset / description
      Previous value: -"Skip this many matches before returning. Use the nextOffset from the previous answer to walk the whole set; its absence means you reached the end."New value: +"Number of matches to skip; the nextOffset of a previous answer continues from there (absent at the end)."
  2. 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"
      +]
  3. 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"
      +}
  4. 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"
      -}
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is added semantics — and it delivers two real caveats: targetArea is 'the issuer's stated audience, not eligibility', and perps carry 'no ownership'. It also notes exact counts live in the response, though it says nothing about how pagination behaves beyond the schema's own offset text.

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?

Dense but front-loaded: the core comparison scope leads, then edge cases and filter notes. The opening clause ('every token on it side by side') is slightly clipped grammatically, but no sentence is filler.

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 shape need not be explained, and annotations carry the safety profile. What remains — scope, the multi-issuer precondition, perp coverage, the targetArea caveat, and the no-query behaviour — is all present for a five-parameter, all-optional read tool.

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%, including enum value examples and the 'Omit to list all' note for `query`, so the schema already carries the parameter burden. The description reinforces query-omission and the existence of sector/industry filters but adds no format or precedence detail beyond the schema. 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?

Names a specific comparison operation and enumerates exactly what is compared: 'every token on it side by side (issuer, structure, KYC gates, custody, chain and each issuer's stated target/area), plus every Hyperliquid perpetual on it (fees, funding, leverage; no ownership).' The scope condition ('tokenized by more than one issuer') and the edge case ('securities that exist on-chain only as a perpetual') make it distinguishable from a plain lookup like find_tokenized_security.

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 selection conditions: omit `query` to list every such security, and sector/industry filters are available for narrowing. It does not name a sibling alternative or state when another tool (e.g. find_tokenized_security) is the better pick, so it stops short of full when/when-not routing.

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