Skip to main content
Glama
Sign In
x402station-mcp

x402station-mcp

by sF1nX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Check watch subscription status + recent alerts

watch_status

Retrieve a watch's current state, including active/expired status, alerts remaining, last 10 delivery attempts, and latest signal snapshot. Requires watch ID and secret.

Instructions

Returns the current state of a watch: active/expired, alerts remaining (out of 100 prepaid), last 10 alert deliveries with their delivery_status, and the last computed signal snapshot. Free — no payment required, secret-gated. The secret is the one returned by watch_subscribe.

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_status"
  }
}

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
Behavior4/5

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

No annotations provided, so description carries the burden. It discloses that the tool reads current state (active/expired, alerts, deliveries, signal), is free, and requires the secret from watch_subscribe. It does not mention error handling or side effects, but for a read-only status tool, the disclosure is adequate.

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?

Three sentences, no fluff. First sentence lists all returned fields. Second notes free and secret-gated. Third ties secret to watch_subscribe. Front-loaded main purpose, every sentence earns its place.

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?

Given no output schema and no annotations, description explains return fields sufficiently (state, alert count, deliveries, signal snapshot). Lacks details on error responses or data format for signal snapshot, but overall adequate for a 2-param read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers both parameters with descriptions (UUID watchId, 64-char hex secret). Description adds value by specifying the secret is the one returned by watch_subscribe, linking to a related tool. This extra context goes beyond 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?

Description clearly states it 'returns the current state of a watch' and enumerates specific fields (active/expired, alerts remaining, last 10 deliveries, signal snapshot). The verb 'returns' and resource 'watch status' are specific, and it distinguishes from sibling tools like watch_subscribe and watch_unsubscribe.

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?

Mentions that the tool is free and secret-gated, linking the secret to watch_subscribe, which implies usage after subscribing. However, it lacks explicit guidance on when not to use it or comparisons to siblings like watch_unsubscribe.

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