Skip to main content
Glama

TokenBank — tokenized real-world assets

Find a tokenized security

find_tokenized_security
Read-onlyIdempotent

Looks up whether a tokenized version of a company, ETF or bond exists, and from which issuer, by company name, ticker or ISIN. Sources: issuer catalogues (Backed / xStocks, Ondo Global Markets, Dinari, Robinhood, Coinbase, Backpack, Reality (Bitget), ST0x, Jarsy, Midas, Lofty), Swiss SME share registers (Aktionariat), Japanese security tokens, El Salvador's CNAD register (registered offerings; sale not confirmed), European and Asian digital bonds from official registers, and an aggregated tier (CoinGecko). One company can be tokenized several times (e.g. Apple as seven tokens); each row states issuer, legal form, chain and targetArea (the issuer's stated audience, not an eligibility check) and its source authority: aggregated rows only observe that a token exists and carry no KYC gate or custody claim. Identity data only: yield, minimum and risk grade are absent, not zero.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "find_tokenized_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineNoBacked only. xstocks = the xStocks line; btokens = the older bToken DeFi line.
limitNoMax results (default 20)
queryYesCompany name, ticker or ISIN — e.g. "Apple", "AAPL", "US0378331005", "Silver Trust"
issuerNoRestrict to one issuer. Omitted: all issuers.
offsetNoNumber of matches to skip; the nextOffset of a previous answer continues from there (absent at the end).
include_haltedNoInclude instruments Backed has flagged as trading-halted. Default false.

Output Schema

NameRequiredDescriptionDefault
matchedYes
readThisNo
cataloguesNo
nextOffsetNoPass as offset to fetch the next page; absent when there is no more
instrumentsYes
issuedByMoreThanOneIssuerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / catalogues / items
      Added value: +{
      +  "type": "object"
      +}
    • changedOutput schema / properties / catalogues / type
      Previous value: -"object"New value: +"array"
    • addedOutput schema / properties / issuedByMoreThanOneIssuer / items / properties
      Added value: +{
      +  "symbols": {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "underlying": {
      +    "type": "string"
      +  }
      +}
    • changedOutput schema / properties / issuedByMoreThanOneIssuer / items / type
      Previous value: -"string"New value: +"object"
  2. Changed2 schema fields changed
    • changedInput schema / properties / issuer / description
      Previous value: -"Restrict to one issuer. Omit to search both, which is usually what you want — the comparison between them is the useful part."New value: +"Restrict to one issuer. Omitted: all issuers."
    • 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)."
  3. Changed1 schema field changed
    • changedInput schema / properties / line / description
      Previous value: -"Backed only. xstocks = retail line via Kraken; btokens = older DeFi line, primary issuance for eligible investors only."New value: +"Backed only. xstocks = the xStocks line; btokens = the older bToken DeFi line."
  4. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already establish a safe, idempotent read, but the description adds real behavioral context the annotations cannot: multi-row results per company ('Apple as seven tokens'), per-row source authority, the caveat that aggregated rows carry no KYC gate or custody claim, that 'sale not confirmed' for the CNAD register, and that targetArea is the issuer's stated audience rather than an eligibility check. This is exactly the kind of provenance and confidence disclosure that prevents an agent from over-reading results.

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?

Front-loaded with the core verb and lookup keys in the first clause, followed by progressive detail. The long enumeration of issuer catalogues and registers is dense but earns its place as provenance information the agent needs to weight results; only the catalogue list borders on laundry-list length.

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 an output schema present and safety annotations covering the mutation profile, the description only needs to explain sources, caveats and interpretive limits — and it does so thoroughly, including the identity-only caveat and the meaning of targetArea. Nothing an agent needs to call or correctly interpret this tool is missing.

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 the schema already documents query, line, issuer, limit, offset and include_halted, including the nextOffset continuation convention. The description reinforces that one company can yield several rows (relevant to limit/offset) and clarifies that issuer filtering exists only for Backed and Ondo via the enum, but adds no syntax or format detail beyond the structured fields.

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 ('looks up whether a tokenized version of a company, ETF or bond exists, and from which issuer') plus the accepted lookup keys (name, ticker, ISIN). This clearly separates it from siblings like compare_tokenized_access (comparison) and find_permissionless_assets (access eligibility) without needing to open a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is strongly implied by the scoping statement 'Identity data only: yield, minimum and risk grade are absent, not zero', which steers an agent away from using this for yield questions. However, no sibling is named as the alternative and there is no explicit when-to-use/when-not-to-use sentence, so routing still requires inference from the sibling list.

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