Skip to main content
Glama
JonasFuchss

x402 Discovery & Trust MCP

by JonasFuchss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

x402 Trust watch: poll event log

x402_watch_events

Poll a watch's event log using watch_id and secret, then page through returned cursors so no events between polls are missed.

Instructions

Poll a watch's event log with watch_id and secret, paging by the returned cursors. Nothing between polls is lost.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNoEndpoint-event cursor: the `next_cursor` from a previous poll. Omit for the first poll.
secretYesThe one-time bearer secret returned by x402_watch_create.
watch_idYesWatch id returned by x402_watch_create.
watch_sinceNoLifecycle-event cursor: the `watch_events_cursor` from a previous poll. Omit for the first poll.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / since / description
      Previous value: -"Cursor: the highest event_id from a previous poll. Omit for the first poll."New value: +"Endpoint-event cursor: the `next_cursor` from a previous poll. Omit for the first poll."
    • addedInput schema / properties / watch_since
      Added value: +{
+  "description": "Lifecycle-event cursor: the `watch_events_cursor` from a previous poll. Omit for the first poll.",
+  "type": "string"
+}
  2. Addedv1.4.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. 'Nothing between polls is lost' is a genuinely useful durability guarantee for a cursor-based poll, but the description says nothing about the one-time bearer secret's handling, rate limits, or error/expiry behavior.

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 short sentences, front-loaded with the action and required inputs, and the durability clause is a deliberate, load-bearing addition. Nothing is padded or redundant.

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 4-parameter polling tool with no annotations and no output schema, the description covers the polling contract but omits what the event log actually returns and how the two distinct cursors (since vs watch_since) relate to different event streams, leaving an agent to learn that only from the 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 both cursors and the two required identifiers are already documented in the schema. The description only restates watch_id/secret and the cursor paging idea, adding no syntax or format detail beyond what the schema provides.

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?

States a specific verb (poll) and resource (a watch's event log), which cleanly separates it from the other x402_watch_* siblings that create, edit, cancel, or renew watches. It does not explicitly name an alternative, but the resource is unambiguous.

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?

The mention of 'paging by the returned cursors' implies an iterative polling loop and hints at how to continue, but there is no explicit when-to-use guidance or statement of when this is preferable to x402_watch_create or the trust/score siblings. Usage is inferable rather than stated.

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