Skip to main content
Glama

Council of AI GSPC

by io.github.CSOAI-ORG
OverviewDiscussionsAdmin

x402 catalog trust snapshot

x402_trust
Read-onlyIdempotent

GET the latest x402 catalog trust snapshot: counts of how many catalogued x402 resources open a correct 402 challenge vs how many are phantom on the wire. Counts only by doctrine — host details withheld; a 402 is NOT delivery; measurement, never certification.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNo
as_ofNo
stateYesVALID or UNREACHABLE
countsNo
sourceNo
headlineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedOutput schema / properties / as_of / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / counts / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / headline / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • addedOutput schema / properties / kind
      Added value: +{}
    • addedOutput schema / properties / source
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / state
      Added value: +{
+  "description": "VALID or UNREACHABLE",
+  "type": "string"
+}
    • addedOutput schema / required
      Added value: +[
+  "state"
+]
  2. Changed7 schema fields changed
    • changedOutput schema / properties / as_of / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • changedOutput schema / properties / counts / type
      Previous value: -[
-  "object",
-  "null"
-]New value: +"object"
    • changedOutput schema / properties / headline / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • removedOutput schema / properties / kind
      Removed value: -{}
    • removedOutput schema / properties / source
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / state
      Removed value: -{
-  "description": "VALID or UNREACHABLE",
-  "type": "string"
-}
    • removedOutput schema / required
      Removed value: -[
-  "state"
-]
  3. Changed7 schema fields changed
    • changedOutput schema / properties / as_of / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / counts / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / headline / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • addedOutput schema / properties / kind
      Added value: +{}
    • addedOutput schema / properties / source
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / state
      Added value: +{
+  "description": "VALID or UNREACHABLE",
+  "type": "string"
+}
    • addedOutput schema / required
      Added value: +[
+  "state"
+]
  4. Added

TDQS

A4.5/5.0
Behavior5/5

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

The description adds meaningful behavioral context beyond the annotations: host details are withheld, counts are doctrine-only, and a 402 is explicitly not delivery. These caveats clarify both scope and limitations in a way the schema and annotations alone would not convey.

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 entire definition is a single dense sentence that front-loads the operation and resource, then packs essential caveats into semicolon-separated clauses. Every phrase earns its place; there is no redundant wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read-only snapshot with an output schema, the description is fully adequate. The annotations cover safety and idempotence, and the description covers semantic limitations. Nothing needed to call this tool correctly is missing.

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?

The tool has zero parameters and 100% schema coverage, so the description has no parameter burden. The baseline of 4 applies; the description appropriately makes clear this is a no-input snapshot call.

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 identifies a specific verb ('GET'), a specific resource ('x402 catalog trust snapshot'), and the exact data being returned (counts of correct 402 challenges vs phantom resources). It is distinct from sibling tools like mcp_trust by focusing on x402 catalog counts, not general trust or individual records.

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 description implies when to use this tool: when you need aggregate x402 catalog trust counts by doctrine. It also warns 'measurement, never certification,' suggesting it should not be used for certification decisions. However, it does not explicitly name alternatives or state exclusion conditions, leaving some inference required.

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

All Council of AI GSPC 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