Skip to main content
Glama
Sign In

SYNTHORA x402 Intelligence Mesh

by com.hergertsynthora
OverviewDiscussionsAdmin

registry_watch

Read-onlyIdempotent

Registry change history from stored registry_delta records, ordered by database timestamp and ID. Query with since (cursor or ISO8601), slug and limit (1..200). Source timestamps and coverage are included; records may be historical and do not prove current endpoint operation, payments or identity. 0.03 USDC on Base. [x402: 0.03 USDC per call on Base]

Input Schema

NameRequiredDescriptionDefault
slugNoOptional exact stored-event slug filter. Surrounding whitespace is trimmed; matching is by equality, not substring search. latest/last/recent/ultimos clear the filter; omitting it requests recent global stored events. This selects historical registry events, not live endpoint health.
limitNoMaximum stored events requested: advertised integer range 1-200, default 50. The current parser converts to an integer and clamps to 1-200; nonnumeric conversion fails. With no since it takes the recent tail, returned chronologically. This limit is not a freshness or coverage guarantee.
sinceNoExclusive cursor del_... or timezone-aware ISO8601 timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum stored events requested: advertised integer range 1-200, default 50. The current parser converts to an integer and clamps to 1-200; nonnumeric conversion fails. With no since it takes the recent tail, returned chronologically. This limit is not a freshness or coverage guarantee."
    • addedInput schema / properties / slug / description
      Added value: +"Optional exact stored-event slug filter. Surrounding whitespace is trimmed; matching is by equality, not substring search. latest/last/recent/ultimos clear the filter; omitting it requests recent global stored events. This selects historical registry events, not live endpoint health."
  2. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / examples
      Previous value: -[
-  {
-    "input": "latest"
-  }
-]New value: +[
+  {
+    "limit": 50
+  }
+]
    • removedInput schema / properties / input
      Removed value: -{
-  "description": "SYNTHORA registry-watch: pay-per-event feed of signed Ed25519 deltas from the x402/M2M endpoint registry — new and changed endpoints, payTos and listings. Pull with {\"since\": \"<cursor|ISO>\", \"slug\": \"",
-  "examples": [
-    "latest"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 50,
+  "examples": [
+    50
+  ],
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Exclusive cursor del_... or timezone-aware ISO8601 timestamp",
+  "type": "string"
+}
    • addedInput schema / properties / slug
      Added value: +{
+  "pattern": "^[A-Za-z0-9_-]{1,128}$",
+  "type": "string"
+}
  3. Changed3 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "input": "latest"
+  }
+]
    • changedInput schema / properties / input / description
      Previous value: -"product parameters (JSON or text). Example: {\"input\": \"latest\"}"New value: +"SYNTHORA registry-watch: pay-per-event feed of signed Ed25519 deltas from the x402/M2M endpoint registry — new and changed endpoints, payTos and listings. Pull with {\"since\": \"<cursor|ISO>\", \"slug\": \""
    • addedInput schema / properties / input / examples
      Added value: +[
+  "latest"
+]
  4. Added
  5. Removed
  6. Changed1 schema field changed
    • changedInput schema / properties / input / description
      Previous value: -"product parameters (JSON or text). Example: {\"input\": \"0x0000000000000000000000000000000000000000\"}"New value: +"product parameters (JSON or text). Example: {\"input\": \"latest\"}"
  7. Added
  8. Removed
  9. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and open-world semantics, so this is the lower bar. The description still adds real context beyond them: source timestamps and coverage are returned, records may be historical, and there is a 0.03 USDC x402 cost per call on Base. That is meaningful behavioral disclosure not present in structured fields.

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?

The description is front-loaded with purpose, then query params, then caveats, then cost, which is a sensible order. The only waste is the cost statement appearing twice ('0.03 USDC on Base' and '[x402: 0.03 USDC per call on Base]'), a mild redundancy that keeps it from a 5.

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?

There is no output schema, so the description must cover return semantics; it does state that source timestamps and coverage are included and that results are ordered by timestamp and ID. With annotations present and all three params documented, the only minor gap is a fuller picture of response shape for a history/feed tool.

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 schema already documents slug, limit and since in detail. The description largely restates the range (1..200) and parameter names; its only marginal addition is the 'not a freshness or coverage guarantee' caveat, which is already echoed in the limit field description. Baseline 3 applies.

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 specific verb and resource: 'Registry change history from stored registry_delta records,' plus the ordering key (database timestamp and ID). This is concrete and distinguishable from generic 'list' tools. It does not, however, explicitly contrast itself with close siblings like port_watch, so differentiation is left to inference.

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?

It tells the agent how to query ('since, slug and limit') and adds an important interpretation caveat that records are historical and do not prove current endpoint operation, payments or identity. But it never names an alternative tool or the condition that would select one, so when-to-use-vs-siblings is only implied.

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

All SYNTHORA x402 Intelligence Mesh toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources