Skip to main content
Glama

Buy BNKR with USDC

build_bnkr_buy
Read-only

Buy BNKR with USDC through 0x (Panda 0.15% + 0x 0.15%). Minimum 0.10 USDC. Then stake it with build_bnkr_stake. Returns unsigned transactions to sign in order (and as one EIP-5792 batch), simulated from the wallet, plus a sign_url for a human owner. Nothing is sent.

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": {
      "wallet": "<wallet>",
      "amount_usdc": "<amount_usdc>"
    },
    "name": "build_bnkr_buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesThe wallet on Base that will sign (and that owns the positions).
amount_usdcYesUSDC to spend, in whole USDC, e.g. "25" or "0.5".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With readOnlyHint already declared, the description still adds substantial context: fees (Panda 0.15% + 0x 0.15%), that nothing is sent, that output is unsigned txs to sign in order, an EIP-5792 batch alternative, a wallet-based simulation, and a sign_url for a human owner. This resolves the apparent tension between a 'buy' verb and readOnlyHint=true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with purpose, then constraint, then routing and return behavior. No filler; every clause carries information.

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?

There is no output schema, yet the description fully describes the return shape (ordered unsigned txs, optional EIP-5792 batch, sign_url) and the safety posture, leaving no material gap for an agent 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 description coverage is 100%, so wallet and amount_usdc are already documented. The description adds only a minimum-amount constraint (0.10 USDC) and unit context, so the baseline 3 is appropriate.

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+resource (buy BNKR with USDC) plus the execution route (0x) and fee split, which clearly separates it from siblings like build_swap or build_bnkr_stake. It also names the natural follow-up tool, so the agent can place it in a flow without opening other schemas.

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 a concrete precondition (minimum 0.10 USDC) and an explicit next step (then stake with build_bnkr_stake), which tells the agent where this fits in the BNKR entry flow. It does not explicitly say when to prefer it over build_swap, so it stops short of full when-not guidance.

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