Council of AI GSPC

RWA asset evidence (paid, x402; preview free)

rwa_evidence

PAID (x402). Per-request signed evidence card of ONE XRPL issued asset's deterministic on-ledger state via https://councilof.ai/api/rwa/evidence: AccountRoot lsf* flags, Domain, the two-way xrp-ledger.toml check (PASS / FAIL / UNCHECKABLE — unreachable is never FAIL), gateway_balances obligation, holders as the free reader has them, every raw fetch sha256'd. preview=true is free (unsigned state). Historical state at fetched_at — not a rating, not a guarantee, not a conformity mark; /api/xrpl and /root.json stay free. Without x_payment the tool returns the 402 challenge. If the route is not deployed on this origin the tool says NOT_DEPLOYED.

Input Schema

TableJSON Schema

Name	Required	Description
`asset`	Yes	Symbol (as listed by https://councilof.ai/api/xrpl) or issuer r-address.
`preview`	No	true = free unsigned state.
`x_payment`	No	The X-PAYMENT header value signed against accepts[] from the previous 402. Omit to receive the challenge.

Output Schema

TableJSON Schema

Name	Required	Description
`tool`	No
`route`	No
`status`	Yes	PAYMENT_REQUIRED, DELIVERED, NOT_DEPLOYED, UNREACHABLE, UNREADABLE_RESPONSE, BAD_ARGUMENTS or HTTP_<code>
`accepts`	No
`resource`	No
`deliverable`	No
`http_status`	No
`x402Version`	No
`delivery_state`	No
`settlement_state`	No
`payment_presented`	No
`not_a_certification`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "The wrapper's status fields. On PAYMENT_REQUIRED (isError:true) the route's x402 PaymentRequired object (x402Version, resource, accepts, extensions) is spread at the top level too, per the x402 MCP transport.",
+  "properties": {
+    "accepts": {
+      "type": "array"
+    },
+    "deliverable": {},
+    "delivery_state": {
+      "type": "string"
+    },
+    "http_status": {
+      "type": "integer"
+    },
+    "not_a_certification": {
+      "type": "boolean"
+    },
+    "payment_presented": {
+      "type": "boolean"
+    },
+    "resource": {
+      "type": "object"
+    },
+    "route": {
+      "type": "string"
+    },
+    "settlement_state": {
+      "type": "string"
+    },
+    "status": {
+      "description": "PAYMENT_REQUIRED, DELIVERED, NOT_DEPLOYED, UNREACHABLE, UNREADABLE_RESPONSE, BAD_ARGUMENTS or HTTP_<code>",
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "x402Version": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 26, 2026

changedOutput schema / (root)

Previous value: -{
-  "description": "The wrapper's status fields. On PAYMENT_REQUIRED (isError:true) the route's x402 PaymentRequired object (x402Version, resource, accepts, extensions) is spread at the top level too, per the x402 MCP transport.",
-  "properties": {
-    "accepts": {
-      "type": "array"
-    },
-    "deliverable": {},
-    "delivery_state": {
-      "type": "string"
-    },
-    "http_status": {
-      "type": "integer"
-    },
-    "not_a_certification": {
-      "type": "boolean"
-    },
-    "payment_presented": {
-      "type": "boolean"
-    },
-    "resource": {
-      "type": "object"
-    },
-    "route": {
-      "type": "string"
-    },
-    "settlement_state": {
-      "type": "string"
-    },
-    "status": {
-      "description": "PAYMENT_REQUIRED, DELIVERED, NOT_DEPLOYED, UNREACHABLE, UNREADABLE_RESPONSE, BAD_ARGUMENTS or HTTP_<code>",
-      "type": "string"
-    },
-    "tool": {
-      "type": "string"
-    },
-    "x402Version": {
-      "type": "integer"
-    }
-  },
-  "required": [
-    "status"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedSep 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "The wrapper's status fields. On PAYMENT_REQUIRED (isError:true) the route's x402 PaymentRequired object (x402Version, resource, accepts, extensions) is spread at the top level too, per the x402 MCP transport.",
+  "properties": {
+    "accepts": {
+      "type": "array"
+    },
+    "deliverable": {},
+    "delivery_state": {
+      "type": "string"
+    },
+    "http_status": {
+      "type": "integer"
+    },
+    "not_a_certification": {
+      "type": "boolean"
+    },
+    "payment_presented": {
+      "type": "boolean"
+    },
+    "resource": {
+      "type": "object"
+    },
+    "route": {
+      "type": "string"
+    },
+    "settlement_state": {
+      "type": "string"
+    },
+    "status": {
+      "description": "PAYMENT_REQUIRED, DELIVERED, NOT_DEPLOYED, UNREACHABLE, UNREADABLE_RESPONSE, BAD_ARGUMENTS or HTTP_<code>",
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "x402Version": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedSep 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description goes far beyond annotations, disclosing the x402 payment flow, the deterministic state contents, the 'unreachable is never FAIL' rule, the sha256 hashing of raw fetches, the historical fetched_at semantics, and the NOT_DEPLOYED behavior. This is rich behavioral context that annotations do not provide.

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 dense but front-loaded with the most important fact ('PAID (x402)') and each clause adds useful detail. It is somewhat long and run-on, but every sentence earns its place for a tool with a payment flow and multiple behavioral caveats.

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?

Given the x402 payment complexity, the output schema already exists, and the description covers payment, preview, failure modes, deployment status, and what the evidence is not, the definition is complete enough for an agent to invoke the tool correctly.

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 coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema by explaining that preview=true yields free unsigned state and that omitting x_payment returns the 402 challenge. This helps the agent understand the payment handshake.

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 opens with 'PAID (x402). Per-request signed evidence card of ONE XRPL issued asset's deterministic on-ledger state' and names the exact endpoint. It clearly identifies the resource and the operation, and the 'not a rating, not a guarantee, not a conformity mark' phrasing helps distinguish it from certification-style sibling tools.

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?

The description gives clear usage context: it is paid, preview=true is free, and omitting x_payment returns the 402 challenge. It does not explicitly name sibling alternatives or state when not to use it, so it stops short of full exclusion guidance.

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 tools Inspect

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

Need Help?