Skip to main content
Glama
Sign In

SwapChan

by io.github.TSavo
OverviewDiscussionsAdmin

SwapChan agent playbook (how to use every tool together)

swapchan_playbook
Read-only

START HERE. Long-form guidance for agents: principles (trustless, human sign-off on every tx, verify before sign, confirm with read_chain, never touch seed phrases, always give short + full links), the full tool catalog with when-to-use, and end-to-end workflows: find-money (find_money/find_money_batch → read_chain → signing_guide/recovery_guide → verify_tx → human sign-off → broadcast_tx → tx_status → build_swap_link/get_quote/build_swap_tx → verify → sign → broadcast), best-swap, rebalance, revoke-approvals, bridge-stuck, token-safety, recover-old-wallet. workflow= for one, full=true (default when no workflow) for everything. How to combine this with the other tools: swapchan_playbook (workflows: find-money, best-swap, rebalance, revoke-approvals, bridge-stuck, token-safety, recover-old-wallet).

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

Input Schema

NameRequiredDescriptionDefault
fullNo
workflowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context about default behavior (full=true when no workflow) and the guidance content, but it does not describe the return format or clarify that the output is static guidance text rather than live data.

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 description is front-loaded with 'START HERE' and useful content, but it is a long run-on paragraph with redundancy: the workflow list appears twice, once in the workflow enumeration and again in the closing sentence about combining with other tools. Trimming the duplicate would improve structure.

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 two-parameter guidance tool with annotations and no output schema, the description is largely complete. It explains what the playbook contains, how to request a single workflow or the full guide, and which workflows are available. A brief note on output format would make it fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It does this well by naming both parameters, listing the valid workflow IDs, and stating that full defaults to true when no workflow is specified. It leaves out edge cases such as invalid workflow handling, but the core semantics are clear.

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?

The description opens with 'START HERE' and clearly states it is long-form guidance for agents, including principles, a full tool catalog, and end-to-end workflows. It distinguishes itself from sibling action tools by being the meta-guide that explains how to use every tool together.

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?

It gives strong usage direction with 'START HERE' and explains how to select a single workflow via workflow=<id> versus retrieving everything via full=true. It lists the available workflows but does not explicitly state when not to use the playbook or contrast it with other tools beyond the implied 'start here' framing.

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

All SwapChan 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