Skip to main content
Glama

Watchlist changes (Pro)

get_watch_status
Read-only

Re-checks watched Solana tokens and reports changes since baseline, such as insider selling, liquidity pulls, holder concentration jumps, authority changes, risk spikes, and price drops.

Instructions

Pro: re-check watched tokens (up to 5 stale ones per call; others use their last check) and report changes since each baseline: dev or insider wallets selling, liquidity pulled or draining, holder concentration jumps, sell test failing, authorities re-enabled, risk score or dump-model spikes, price halving. Automated risk signals, not financial advice. A low score is not a recommendation to buy.

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

Input Schema

NameRequiredDescriptionDefault
api_keyNoRugRadar Pro API key (optional; alternatively send Authorization: Bearer <key>).
reset_baselinesNoAfter reporting, make the current readings the new baselines

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior1/5

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

The description discloses that reset_baselines makes current readings the new baselines, which is a state mutation. This contradicts the readOnlyHint=true annotation, so the behavioral claim conflicts with structured metadata.

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 front-loads the Pro re-check action and then lists the change categories efficiently. The risk disclaimer adds length but is relevant context for interpreting results.

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, no-output-schema tool, the description covers what is checked, the stale-token limit, baseline behavior, and categories of reported changes. The main gap is that it does not describe the response shape, but the change categories provide substantial context.

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 both api_key and reset_baselines are already documented in the schema. The description repeats the reset effect and adds the five-stale-token processing limit, but does not add much parameter-level meaning beyond the schema.

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 states a specific verb and resource: re-check watched tokens and report changes since each baseline. It clearly distinguishes this from watch/unwatch behavior by focusing on re-checking and diff reporting, though it does not name sibling tools explicitly.

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 the note that it re-checks up to 5 stale watched tokens per call while others use their last check. There is no explicit when-to-use guidance versus alternatives such as check_token or watch_token.

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