Skip to main content
Glama
Sign In
x402station-mcp

x402station-mcp

by sF1nX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Unsubscribe from a watch (deactivate)

watch_unsubscribe

Deactivate a watch to stop all further alerts. Subscription history is retained for audit, and no additional notifications are delivered.

Instructions

Deactivates the watch — no further alerts will be queued or delivered. The subscription is set is_active=false but the row + alert history is retained for audit. Free — no payment required, secret-gated. There is no refund for unused prepaid alerts.

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>",
      "secret": "<secret>"
    },
    "name": "watch_unsubscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
watchIdYesThe watchId UUID returned by watch_subscribe.
secretYesThe 64-char hex secret returned by watch_subscribe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.10

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: deactivation, cessation of alerts, row+history retention, free, secret-gated, and no refund. This is comprehensive for the tool's action.

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?

The description is three succinct sentences with no redundancy. It is front-loaded with the primary action and uses minimal but informative language.

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 tool with two parameters and no output schema, the description covers the main points. It lacks potential error cases but is otherwise 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 100% with both parameters well-described. The description does not add new meaning beyond the schema, so baseline 3 is appropriate.

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?

The description clearly states it deactivates a watch and explains the effect: no further alerts, is_active=false, and retention of history. This distinguishes it from the sibling watch_subscribe.

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?

The description provides clear context: it deactivates a watch, is free, secret-gated, and there is no refund. It implies when to use (stop alerts) but does not explicitly mention when not to use or alternatives.

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

Deploy Server

Other Tools