Skip to main content
Glama
JonasFuchss

x402 Discovery & Trust MCP

by JonasFuchss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

x402 Trust watch: create 30-day endpoint monitor

x402_watch_create

Monitor an x402 endpoint for 30 days with alerts on payTo or price changes, delisting, spec regressions, and downtime via polling or webhooks; returns a one-time secret.

Instructions

30-day monitor for one endpoint with alerts on payTo or price changes, delisting, spec regressions and downtime, via polling or webhooks. Returns a one-time secret, keep it.

Input Schema

NameRequiredDescriptionDefault
eventsNoEvent types to subscribe to (default all): payto_change, price_change, asset_network_change, spec_regression, delisting, liveness_down, liveness_recovered, liveness_flapping, latency_regression.
endpointYesFull x402 resource URL to watch. It must already be in our observation set.
slack_urlNoOptional Slack or Discord incoming webhook URL(s). Single string or array; max 5.
webhook_urlNoOptional signed HTTPS webhook URL(s) for push delivery. Single string or array; max 5.
liveness_sensitivity_nNoConsecutive missed probes before liveness_down surfaces to you (1=paranoid … 10=relaxed; default 2).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • changedInput schema / properties / events / description
      Previous value: -"Event types to subscribe to (default all): payto_change, price_change, asset_network_change, spec_regression, delisting, liveness_down, liveness_recovered, latency_regression."New value: +"Event types to subscribe to (default all): payto_change, price_change, asset_network_change, spec_regression, delisting, liveness_down, liveness_recovered, liveness_flapping, latency_regression."
  2. Changed6 schema fields changedv1.5.0
    • addedInput schema / properties / slack_url / $ref
      Added value: +"#/properties/webhook_url"
    • changedInput schema / properties / slack_url / description
      Previous value: -"Optional Slack or Discord incoming webhook URL for push delivery."New value: +"Optional Slack or Discord incoming webhook URL(s). Single string or array; max 5."
    • removedInput schema / properties / slack_url / type
      Removed value: -"string"
    • addedInput schema / properties / webhook_url / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / webhook_url / description
      Previous value: -"Optional signed HTTPS webhook URL for push delivery."New value: +"Optional signed HTTPS webhook URL(s) for push delivery. Single string or array; max 5."
    • removedInput schema / properties / webhook_url / type
      Removed value: -"string"
  3. Addedv1.4.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose real behavioral traits: a fixed 30-day lifetime, one-endpoint scope, push-vs-poll delivery, and that a one-time secret is returned and must be kept. It omits auth/permission requirements, whether the watch starts immediately, quota limits, and what happens at expiry (silent stop vs. transition to a renew state).

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?

Two tight sentences with no filler; the scope ('one endpoint'), lifetime ('30-day'), and delivery modes are front-loaded, and the closing 'Returns a one-time secret, keep it.' efficiently flags the one operational gotcha an agent must not miss.

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 creation tool with no output schema, naming the one-time secret return covers the most important return value. However, a 5-parameter mutation of nontrivial state should also mention the observation-set precondition, auth needs, and the follow-up tools (watch_events, watch_renew, watch_cancel) needed to make the watch useful.

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 baseline is 3 and the schema already documents event names, webhook URL formats, max-5 limits, and liveness sensitivity. The description adds only loose correspondence between alert categories and the events parameter, without new syntax or default details.

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 concrete resource (a 30-day monitor for one endpoint) and enumerates the alert conditions it covers (payTo/price changes, delisting, spec regressions, downtime), which is far more specific than a restated title. It implies creation via the one-time secret return, but never explicitly contrasts itself with x402_watch_edit, x402_watch_cancel, or x402_watch_renew, so sibling differentiation is left to the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to create a watch versus editing, renewing, or cancelling one, nor a pointer to x402_watch_events for consuming alerts. The schema's important precondition that the endpoint 'must already be in our observation set' is never surfaced in the description, so an agent could call this on an unobserved URL without warning.

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