Skip to main content
Glama

Stop watching (Pro)

unwatch_token
Idempotent

Pro: remove a token from this key's agent watchlist.

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": {
      "mint": "<mint>"
    },
    "name": "unwatch_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYes
api_keyNoRugRadar Pro API key (optional; alternatively send Authorization: Bearer <key>).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a non-read-only, non-destructive, idempotent, closed-world mutation. The description adds one piece of context beyond that: the operation requires Pro entitlement, which matters for auth planning. It does not say how removal behaves for an unwatched token or how failures are reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the scope qualifier and Pro gate both arrive before any would-be detail. Nothing is wasted.

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?

For a two-parameter mutation with full annotations and no output schema, the essentials (what is removed and from whose watchlist) are present. Still missing is enough on mint's expected form and on edge-case behavior to call it complete.

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 coverage is 50% — api_key is documented inline while mint has only length bounds. The description clarifies that the string identifies 'a token', narrowing mint's meaning, but it does not specify that mint is a base58 mint address or what the accepted format is.

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 pair ('remove a token') scoped to 'this key's agent watchlist', which clearly separates it from watch_token and get_watch_status by inference. The 'Pro:' prefix identifies it as a premium-tier operation. It stops short of naming the sibling it is the inverse of, so it is not a 5.

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 only implied: an agent can infer this is the removal counterpart to watch_token. There is no explicit statement of when to prefer it, no prerequisites beyond the 'Pro' tag, and no mention of what happens if the token was never watched.

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.