Council of AI GSPC

Commission a measurement card (paid, x402)

commission_card

PAID (x402). Commission one signed card-v0 receipt (surface ras.commission) for a named subject on the frozen bank via https://councilof.ai/api/request-attestation. Re-serves every signed measurement card already on file for the subject; a payment never mints a MEASURED cell (fresh_run stays UNMEASURED until a published run exists). Without x_payment the tool returns the 402 challenge (accepts[] with asset, amount, payTo) plus a free preview of the cards already on file. Measurement, not certification — never a rank, a grade or a certificate. Verification stays free.

Input Schema

TableJSON Schema

Name	Required	Description
`axis`	No	Optional axis slug; omit for the subject-level commission.
`subject`	Yes	Subject to commission: a model id, instrument id or card sha (1-120 chars of [A-Za-z0-9._:/@+-]).
`x_payment`	No	The X-PAYMENT header value (base64 x402 payload) signed by your wallet 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 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond annotations by disclosing the paid x402 nature, the re-serving behavior, and that 'a payment never mints a MEASURED cell (fresh_run stays UNMEASURED until a published run exists).' Also describes the no-payment fallback response and the semantic boundary against certification.

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?

Dense but every sentence earns its place: main action, payment semantics, challenge mode, and scope boundaries. Front-loaded with 'PAID (x402)' and the core action before 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?

For a paid x402 tool with three parameters and an output schema, the description covers the full call flow: challenge without payment, completion with payment, effects on existing cards and fresh_run, and the boundary against certification. Nothing needed to invoke it 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?

Schema coverage is 100%, so the baseline is 3, but the description adds behavioral meaning to the parameters: the x_payment challenge/response flow, what 'subject' can be (model id, instrument id, card sha), and the effect on fresh_run state. This goes beyond the schema's property descriptions.

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?

States the specific action 'Commission one signed card-v0 receipt' for a named subject on the frozen bank, via a concrete endpoint. It also draws clear boundaries: 'Measurement, not certification — never a rank, a grade or a certificate,' distinguishing it from verification and certification tools in the sibling list.

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?

Explains the two-step usage: omit x_payment to get the 402 challenge and free preview, then supply x_payment to complete. It excludes certification and notes 'Verification stays free,' steering agents toward free verification alternatives, though it does not name the specific sibling tool.

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.

Commission a measurement card (paid, x402)

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources