Skip to main content
Glama

TokenBank — tokenized real-world assets

How agents buy tokens

get_agent_buying_guide
Read-onlyIdempotent

Reference data on how an AI agent or trading bot buys tokens with its own wallet: the six steps from wallet to confirmed purchase with the matching MCP/API call for each, the purchase paths (wallet only / owner onboarded once / platform account) with live counts, which asset classes a self-custody wallet can reach without an identity check, the highest-yield wallet-only candidates, decision checks with the fields that answer them (howToDecide: checks, not recommendations), common wallet-policy guardrails, and related guides with JSON URLs.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many candidates (default 10)
min_yield_pctNoOnly list candidates at or above this stated yield, in percent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds that the payload includes live counts and related-guide JSON URLs, implying dynamic data and further navigable references, but says nothing about payload size, freshness, or what happens when the yield filter excludes everything.

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, but the body is one sprawling sentence enumerating eight content areas, which is dense and hard to scan. Every clause does carry content, but a short list would communicate the same information with far less parsing effort.

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?

For a read-only reference tool with two fully documented parameters and no output schema, the description covers the content areas well and even notes that related guides carry JSON URLs. It falls short only in not clarifying how this guide differs from the adjacent step and coverage tools.

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% and both parameters (limit, min_yield_pct) are documented with defaults and bounds in the schema. The description's mention of 'highest-yield wallet-only candidates' hints at how min_yield_pct interacts with the candidate list, but adds no syntax or behavior beyond the schema.

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 specific subject: reference data on how an AI agent or trading bot buys tokens with its own wallet, and itemizes what the payload covers (six steps, purchase paths, asset classes, yield candidates, decision checks). It does not differentiate itself from siblings such as get_purchase_steps, whose subject (the step sequence) is also claimed here, so the agent cannot tell which one to prefer from the description alone.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, nor any named alternative. The parenthetical 'howToDecide: checks, not recommendations' clarifies the nature of the content but is not invocation guidance, leaving the agent to infer that this is a first-call orientation tool.

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