Skip to main content
Glama
Sign In

Agent Kiosk — 23-in-1 B2A Intelligence, Action & x402 API

by io.github.ralf9090
OverviewDiscussionsAdmin

defi_swap_quote

Read-onlyIdempotent

Executable DeFi Swap & Cross-Chain Bridge Action Calldata Builder ($0.05 USDC). Queries LI.FI and ParaSwap aggregators to compute the best DEX/Bridge route and returns ready-to-sign EVM transaction calldata (to, data, value, gasLimit) on Base, Ethereum, Arbitrum, Polygon, and Optimism.

Input Schema

NameRequiredDescriptionDefault
amountNoAmount of from_token to swap (human-readable e.g. '10' or atomic units)
walletNoOptional 0x sender wallet address for transaction simulation
to_chainNoDestination blockchain network (default: same as from_chain)
to_tokenYesDestination token symbol (e.g., 'ETH', 'USDC', 'AERO', 'cbBTC') or 0x address
x_api_keyNoOptional ak_live_... 30-day Prepaid API Pass key to unlock the full unmasked dataset
from_chainNoSource blockchain network (default: 'base')
from_tokenYesSource token symbol (e.g., 'USDC', 'ETH', 'AERO') or 0x contract address
payment_signatureNoOptional x402 v2/v1 Base64 or JSON EIP-3009 USDC payment signature to unlock the full unmasked dataset directly via MCP

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / payment_signature
      Added value: +{
+  "description": "Optional x402 v2/v1 Base64 or JSON EIP-3009 USDC payment signature to unlock the full unmasked dataset directly via MCP",
+  "type": "string"
+}
    • addedInput schema / properties / x_api_key
      Added value: +{
+  "description": "Optional ak_live_... 30-day Prepaid API Pass key to unlock the full unmasked dataset",
+  "type": "string"
+}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered. The description adds real value beyond that: a $0.05 USDC cost, the specific return payload shape, the supported chains, and the aggregator sources. It stops short of explaining rate limits or what the masked vs unmasked dataset difference means operationally.

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?

Two dense sentences that front-load the core capability, cost, and return contract. Slightly packed with branded terminology, but nothing is wasted.

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 usefully enumerates the returned calldata fields and supported networks, and it flags the payment mechanics. It leaves the interaction between x_api_key/payment_signature and the paid $0.05 call somewhat implicit, but the essential call context is present.

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 every parameter is already documented, and the description adds no per-parameter syntax beyond restating the supported chains. Baseline 3 is appropriate when the schema carries the parameter burden.

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 precise verb chain (queries aggregators, computes best route, returns calldata) and names the concrete resource: ready-to-sign EVM transaction calldata. The mention of LI.FI and ParaSwap plus the exact returned fields (to, data, value, gasLimit) clearly distinguishes it from siblings like defi_yields or evm_tx_simulator.

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?

Implies usage (build a swap/bridge route for signing) and surfaces the cost and payment/API-key unlock path, but never states when to pick this over evm_tx_simulator or how the quote flows into execution. No explicit when/when-not or named alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Kiosk — 23-in-1 B2A Intelligence, Action & x402 API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources