Skip to main content
Glama

Watch a token (Pro)

watch_token
Idempotent

Add a Solana token to an agent watchlist (up to 25) and store a baseline risk snapshot; poll get_watch_status to detect changes in score, liquidity, holders, and authorities.

Instructions

Pro: add a token to this key's agent watchlist (up to 25). RugRadar stores a baseline snapshot (score, liquidity, holder concentration, dev and insider holdings, sell test, authorities). Poll get_watch_status to see what changed. There are no push notifications over MCP; for push alerts use the Telegram bot.

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": {
      "query": "<query>"
    },
    "name": "watch_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesMint address, link or $TICKER
api_keyNoRugRadar Pro API key (optional; alternatively send Authorization: Bearer <key>).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, it discloses what state gets created (a baseline snapshot: score, liquidity, holder concentration, dev/insider holdings, sell test, authorities), the watchlist cap, and the delivery model (poll-based, no push). 'Pro' signals an auth/plan prerequisite, which is consistent with the api_key parameter and the non-readOnly annotation.

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?

Front-loads the operation and cap in the first clause, then layers the stored snapshot, the polling path, and the push-alert exclusion. The dense parenthetical field list is justified but pushes it slightly past minimal length.

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?

Covers the mutation's side effects, the cap, and how to observe results, which is what matters for a two-parameter tool with full schema coverage and annotations. It never says what watch_token itself returns, a minor gap given there is no output schema.

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 the mint-address/link/$TICKER forms and the api_key/Bearer alternative are already documented. The description only reinforces the token-identifier meaning of 'query' and the Pro tier requirement, adding little syntax detail beyond the schema.

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?

States a specific verb and resource ('add a token to this key's agent watchlist'), adds the 25-entry cap, and implicitly separates it from unwatch_token and get_watch_status. An agent knows exactly what operation this performs without opening the schema.

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?

Gives the follow-up path explicitly ('Poll get_watch_status to see what changed') and rules out a class of behavior ('no push notifications over MCP; for push alerts use the Telegram bot'). It does not state when to prefer check_token over watch_token, so the routing guidance is clear but not exhaustive.

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