Skip to main content
Glama

ERC-8004 Trustless Agent Identity, Reputation & KYB Escrow MCP

Plan Portfolio Drift & Build Spend-Capped 0.25% Multi-DEX Swap Calldata

plan_and_build_guarded_rebalance_swap
Read-onlyIdempotent

Reads live ETH + USDC wallet balances, enforces maxSpendCapUsd, and assembles ready-to-sign non-custodial multi-DEX swap calldata saving 71% vs standard wallet swap fees.

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

Input Schema

NameRequiredDescriptionDefault
chainIdNoEVM chain ID (default '8453')
targetEthPctNoTarget ETH allocation % from 0 to 100 (default 50)
walletAddressNoAgent or user 0x wallet address
maxSpendCapUsdNoMax USD allowed for this rebalance leg (default 500)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered; the description usefully adds that balances are read live, that the cap is enforced, and that output is non-custodial, unsigned calldata. However it does not disclose what happens when maxSpendCapUsd is exceeded, whether the returned calldata must be broadcast elsewhere, or any approval prerequisite. The 'saving 71% vs standard wallet swap fees' clause is an unverifiable marketing claim rather than behavioral disclosure.

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?

A single front-loaded sentence covering read, constrain, and produce; no filler or repetition of the title. The only dead weight is the 71% fee-savings claim, which does not help an agent decide or invoke correctly.

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

Completeness3/5

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

With four optional params, all defaulted, and no output schema, the definition needs to describe what the calldata result looks like and where it goes next, but it only says 'ready-to-sign'. For a tool whose whole value is a generated transaction payload, missing return-shape and follow-up-step guidance is a real gap, though the constraint semantics are adequately conveyed.

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 all four parameters (chainId, targetEthPct, walletAddress, maxSpendCapUsd) are already documented and the baseline is 3. The description reinforces the meaning of maxSpendCapUsd ('enforces') as a hard constraint rather than a hint, but adds nothing for targetEthPct, which is the core drift parameter and whose effect on the resulting swap is left unexplained.

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 concrete actions and a resource: reads ETH/USDC balances, enforces maxSpendCapUsd, and assembles ready-to-sign multi-DEX swap calldata. That is far more specific than the name alone, though it never mentions the portfolio-drift planning implied by 'plan_and_build_guarded_rebalance_swap' and the title, so the 'plan' half of the tool is unstated.

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 guidance and no alternative named, despite siblings like simulate_evm_tx_and_spend_firewall or build_erc7715_and_coinbase_spend_permission that an agent would need to choose between. The agent must infer that this precedes simulation/broadcast and that it is preferred over a manual swap.

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.