Skip to main content
Glama
Sign In

SwapChan

by io.github.TSavo
OverviewDiscussionsAdmin

List watched tokens

list_watches
Read-only

Show everything on a watchlist (thresholds, prices when added, last check). 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": "list_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.7/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, non-open-world operation. The description adds useful behavioral context by stating that the result includes a display markdown block with chan images and instructing the agent to show it to the user, though it does not cover empty-list or error behavior.

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?

The description is front-loaded with the primary action and result behavior, and it stays reasonably short. The final sentence listing many playbook workflows is somewhat broad but still provides actionable cross-tool context.

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 simple one-parameter read-only list tool, the description provides enough context: what it returns and how to present it to the user. It could be richer about empty results or failure modes, but the schema and annotations cover most remaining structured details.

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 only one parameter and schema description coverage is 100%, so the schema already fully documents watchId, including its pattern and purpose. The description does not add parameter semantics beyond what the schema provides, making the baseline 3 appropriate.

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 uses a clear verb and resource: it shows everything on a watchlist and names the returned fields (thresholds, prices when added, last check). It is understandable without opening the schema, but it does not explicitly distinguish itself from siblings such as check_watches or watch_token.

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?

It gives some integration guidance by pointing to swapchan_playbook workflows, but it does not say when to use list_watches versus check_watches or the watch/unwatch tools. Usage is implied rather than explicitly scoped with alternatives or exclusions.

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