Skip to main content
Glama
Sign In

SwapChan

by io.github.TSavo
OverviewDiscussionsAdmin

Check watchlist

check_watches
Read-only

Check every watched token now: current price, % change since added, which thresholds triggered, and better-route alerts for watched swaps. Each item has a swapUrl. When something triggered, tell the user and offer the SwapChan swap (take profit to USDC, buy the dip, or the better route). Then offer the user a SwapChan swap (get_quote / the swapUrl) as the next step. Result includes display markdown with chan images: show it to the user. 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

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": {
      "watchId": "<watchId>"
    },
    "name": "check_watches"
  }
}

Input Schema

NameRequiredDescriptionDefault
watchIdYesClient-generated random id (8-64 chars [A-Za-z0-9_-]). Generate once, remember it; it is the only key to the list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint/openWorldHint, and the description adds real behavioral context on top: results carry a `display` markdown blob with chan images that must be shown to the user, each item carries a swapUrl, and triggering requires user notification. It does not cover empty-watchlist or invalid-watchId behavior, but the presentation contract is valuable and non-obvious.

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 and scannable, but the middle section repeats itself — 'offer the SwapChan swap' appears in two consecutive sentences with overlapping content (USDC take-profit / buy-the-dip / better route, then get_quote / swapUrl). The trailing playbook enumeration of seven workflow slugs is a long tail of marginal value for this specific tool.

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 carries the return-value burden and does so reasonably: it names the fields returned, the required `display` rendering step, and the swapUrl handoff. Only edge cases (empty list, unknown watchId, rate/refresh semantics) are absent, which is a minor gap for a single-parameter read tool.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains the client-generated id, its pattern, and that it is the only key to the list. The description adds nothing about watchId, so the schema does all the work — baseline 3 applies.

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 gives a specific verb+resource ('Check every watched token now') and enumerates exactly what is returned: current price, % change since added, triggered thresholds, better-route alerts, and swapUrl per item. That clearly separates it from watch_token/unwatch_token and list_watches, though it never names a sibling explicitly, so the differentiation is inferred rather than stated.

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?

Usage is implied by 'check ... now' (on-demand status poll) and the follow-up flow is described (notify the user on trigger, then offer a SwapChan swap via get_quote or the swapUrl). However, there is no statement of when to prefer this over list_watches, and no when-not guidance or error/prerequisite conditions.

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