Skip to main content
Glama

TokenBank — tokenized real-world assets

Find an answer page

find_answer
Read-onlyIdempotent

Matches a natural-language question (e.g. "can I buy Tesla as a token", "best stablecoin yield on Base", "euro stablecoins MiCA", "pre-IPO OpenAI token") against TokenBank answer pages. Returns the best-matching questions with the first sentence of each computed answer (figures from the live dataset), the page URL and a JSON URL with every row, plus matching guides (e.g. how to verify a contract, what happens if an issuer fails), each with a JSON URL. Questions in Arabic, German, Spanish, Japanese, Chinese, Korean, Thai, Vietnamese or Indonesian also return pages written in that language (localPages).

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_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many answers (default 3)
queryYesThe question, in plain words

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds real value beyond that by describing what comes back: best-matching questions with the first sentence of each computed answer, page URL, full-row JSON URL, and matching guides with their own JSON URLs.

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 purpose and return shape are front-loaded in the first sentence, and every clause carries information. The second sentence is long and dense with the language list, but it conveys a genuine behavioral trait rather than filler.

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 no output schema, the description properly takes on the burden of explaining return values, including the JSON URLs and guide results. Minor gaps remain around ranking behavior and how the limit affects the mix of questions versus guides, but an agent has enough to call it correctly.

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 coverage is 100%, so both the query string and the limit parameter (min 1, max 10, default 3) are already documented. The description reinforces that the query should be phrased as a natural-language question, but says nothing about limit or how it affects results, so the baseline of 3 applies.

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 states a specific verb and resource: matching a natural-language question against TokenBank answer pages, with concrete example queries. It is clear what the tool does, but it does not explicitly differentiate itself from search-oriented siblings such as find_tokenized_security or find_permissionless_assets.

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?

The example questions ("can I buy Tesla as a token", "euro stablecoins MiCA") make the intended input context clear, and the note about non-English questions returning localPages clarifies an important usage case. There are no explicit exclusions or named alternatives telling the agent when not to use it.

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