Skip to main content
Glama

TokenBank — tokenized real-world assets

Market coverage by country

get_market_coverage
Read-onlyIdempotent

Per country, whether this dataset can read the local tokenized-asset market, and why not where it cannot (e.g. a permissioned bank consortium chain in Japan, sandbox issuance in Korea, no local-currency stablecoin in India, Vietnam, Indonesia or Thailand). Covers questions such as "what is tokenized in Japan / Korea / Brazil". Without country it lists every market.

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

Input Schema

NameRequiredDescriptionDefault
countryNoCountry slug or name, e.g. japan, korea, brazil, india, switzerland. Omit to list all.
readable_onlyNoOnly markets whose instruments we can actually read (default false — the closed ones are the point)

Output Schema

NameRequiredDescriptionDefault
marketNo
marketsNo
summaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "required": [
      +      "markets"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "market"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / market
      Added value: +{
      +  "type": "object"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "markets"
      -]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered; the description adds the substantive behavioral point that the output deliberately includes the negative cases and the reasons behind them. It also clarifies the default listing behavior when no country is supplied. It does not discuss volume, pagination or freshness, which would be the remaining useful detail for a read lookup.

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?

The core claim (readable or not, and why not) is front-loaded in the first clause, with examples confined to parentheses. The parenthetical example list is long and slightly heavy, but every item illustrates a distinct failure mode rather than padding. No redundant restatement of the title or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return shape needs no explanation, annotations cover the safety profile, and both parameters are fully described. The description supplies the domain framing an agent needs to recognize when coverage-and-reason is the right answer. Only the missing sibling-level routing keeps it from a 5.

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 both parameters are already documented, including the default of `readable_only` and the effect of omitting `country`. The description reinforces the omit-country listing behavior but adds no format, slug-acceptance or edge-case meaning beyond what the schema states. Baseline 3 is appropriate when the schema carries the semantics.

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?

The description names a specific resource and the exact question it answers: per country, whether the dataset can read the local tokenized-asset market, plus the reason when it cannot. Concrete examples (Japanese bank consortium chain, Korean sandbox issuance, missing INR/VND/IDR/THB stablecoins) make the scope unmistakable. It does not explicitly distinguish itself from near-neighbors like compare_tokenized_access or get_country_registers, so it stops short of a 5.

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 implied rather than stated: it says it 'covers questions such as "what is tokenized in Japan / Korea / Brazil"' and that omitting `country` lists every market. There is no explicit when-to-use versus the sibling comparison tools, and no guidance on when coverage questions belong here rather than in compare_tokenized_access. Adequate but leaves routing to inference.

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