Skip to main content
Glama

Council of AI GSPC

by io.github.CSOAI-ORG
OverviewDiscussionsAdmin

Article 50 marking evidence (paid, x402; preview free)

art50_marking_evidence

PAID (x402 or CSOAI LTD invoice). Article 50 marking-evidence pack via https://councilof.ai/api/art50/marking-evidence: which machine-readable marks the named methods DETECT in these bytes right now. Scope: C2PA and IPTC metadata only (C2PA manifest store, assertion hashes, hard binding, claim signature; IPTC digitalSourceType); no watermark, fingerprint or other kind of mark is read. NOT_DETECTED is not unmarked: Article 50(2) is technology-neutral, so a mark this pack cannot read may be present, and metadata is often stripped on re-save. Disclosure: CSOAI is a member of the C2PA, whose specification is one of the two methods read. The pack carries the verbatim Art 50(2) text hash and the dates it turns on. Point-in-time detection — never a conformity opinion, never a compliance word of any kind. preview=true is free and returns the same measurement unsigned. Without x_payment the tool returns the 402 challenge. If the route is not deployed on this origin the tool says NOT_DEPLOYED rather than inventing a result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoPublic HTTP(S) URL of the generative output to measure (≤20 MiB). The server fetches only this declared measurement subject.
previewNotrue = free unsigned measurement (no card sha, no signature).
bytes_b64NoAlternatively the output bytes, base64 (≤20 MiB decoded).
x_paymentNoThe X-PAYMENT header value signed against accepts[] from the previous 402. Omit to receive the challenge.
manifest_b64NoAlternatively a detached C2PA manifest store, base64 (manifest-only mode).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolNo
routeNo
statusYesPAYMENT_REQUIRED, DELIVERED, NOT_DEPLOYED, UNREACHABLE, UNREADABLE_RESPONSE, BAD_ARGUMENTS or HTTP_<code>
acceptsNo
resourceNo
deliverableNo
http_statusNo
x402VersionNo
delivery_stateNo
settlement_stateNo
payment_presentedNo
not_a_certificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / url / description
      Previous value: -"Public http(s) URL of the generative output to measure (≤20 MiB)."New value: +"Public HTTP(S) URL of the generative output to measure (≤20 MiB). The server fetches only this declared measurement subject."
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • addedInput schema / properties / url / maxLength
      Added value: +2048
    • addedInput schema / properties / url / pattern
      Added value: +"^https?://"
  2. Changed4 schema fields changed
    • changedInput schema / properties / url / description
      Previous value: -"Public HTTP(S) URL of the generative output to measure (≤20 MiB). The server fetches only this declared measurement subject."New value: +"Public http(s) URL of the generative output to measure (≤20 MiB)."
    • removedInput schema / properties / url / format
      Removed value: -"uri"
    • removedInput schema / properties / url / maxLength
      Removed value: -2048
    • removedInput schema / properties / url / pattern
      Removed value: -"^https?://"
  3. Changed4 schema fields changed
    • changedInput schema / properties / url / description
      Previous value: -"Public http(s) URL of the generative output to measure (≤20 MiB)."New value: +"Public HTTP(S) URL of the generative output to measure (≤20 MiB). The server fetches only this declared measurement subject."
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • addedInput schema / properties / url / maxLength
      Added value: +2048
    • addedInput schema / properties / url / pattern
      Added value: +"^https?://"
  4. Changed1 schema field changed
    • 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"
+}
  5. Changed1 schema field changed
    • 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
  6. Changed1 schema field changed
    • 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"
+}
  7. Changed1 schema field changed
    • 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
  8. Changed1 schema field changed
    • 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"
+}
  9. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With annotations present (readOnlyHint=false, openWorldHint=true), the description goes well beyond them: it discloses the paid x402 flow, the 402 challenge behavior, the point-in-time/caveat semantics (NOT_DETECTED != unmarked, metadata often stripped), the C2PA membership disclosure, and the explicit refusal to render conformity/compliance opinions.

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?

Dense but front-loaded, leading with PAID and the core detection claim before scope, caveats and payment mechanics. Most sentences carry distinct weight, though the run-on structure and repetition of the payment/preview point cost it a top score.

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?

An output schema exists, so return values need not be explained. The description covers the remaining burden for a paid, network-fetching, point-in-time measurement tool: scope limits, failure modes, payment handshake and evidentiary caveats are all present.

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% with zero required parameters, so the schema already documents url, preview, bytes_b64, x_payment and manifest_b64. The description reinforces the payment semantics (x_payment omission yields the challenge; preview is free/unsigned) but adds no syntax or format detail beyond the schema.

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?

Names a specific verb (measure/detect) and resource (Article 50 marking-evidence pack) and immediately bounds the scope: 'which machine-readable marks the named methods DETECT in these bytes right now. Scope: C2PA and IPTC metadata only.' It explicitly excludes watermark/fingerprint marks, so an agent can tell it apart from other evidence 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?

Gives clear operating conditions: preview=true is free and unsigned, omitting x_payment returns the 402 challenge, and an undeployed route returns NOT_DEPLOYED. It does not, however, explicitly route the agent among siblings such as evidence_bundle, rwa_evidence, or server_evidence.

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