Skip to main content
Glama

Verify a signed measurement card (free)

verify_card
Read-onlyIdempotent

Verify a signed gspc.measurement-card under the published rule (https://councilof.ai/signed/HOW-TO-VERIFY.md): recompute the id from the canonical body bytes, then check the Ed25519 signature under a key PINNED in this verifier and published in the did:web:csoai.org DID document: #card-attestation-1 (the card key of the signed card index) or #card-attestation-2 (the card key added on rotation, 27 Sep 2026; a card names the key it was signed under), plus the board key for the cards it signed. pinned_key in the result names the key that matched. A card that carries its own key proves only that the file is self-consistent — anyone can alter a body and sign it with a key they just generated — so an inline key outside the pinned set is reported INVALID, and a DID key reference outside it UNCHECKABLE. Three verdicts, never two: VALID, INVALID (with the reason), or UNCHECKABLE when the check could not be completed — 'could not check' is a different claim from 'forged'. Accepts the card as a JSON object, a JSON string, a councilof.ai / csoai.org URL, or a 64-hex card id (the record id shown on the site and the card field of list_cards), which resolves to https://councilof.ai/signed/cards/{id}.json. Never a certification.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardYesThe signed card: an object, a JSON string, a councilof.ai / csoai.org URL to one, or a 64-hex card id (resolved to https://councilof.ai/signed/cards/{id}.json).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
noteNo
ruleNo
stateYesVALID, INVALID or UNCHECKABLE
checksNo
familyNo
reasonNo
reasonsNo
pinned_keyNo
resolved_fromNoPresent when a 64-hex card id was passed: the id asked about and the URL fetched for it.
not_a_certificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / card / description
      Previous value: -"The signed card: an object, a JSON string, or a councilof.ai / csoai.org URL to one."New value: +"The signed card: an object, a JSON string, a councilof.ai / csoai.org URL to one, or a 64-hex card id (resolved to https://councilof.ai/signed/cards/{id}.json)."
    • addedOutput schema / properties / resolved_from
      Added value: +{
      +  "description": "Present when a 64-hex card id was passed: the id asked about and the URL fetched for it.",
      +  "properties": {
      +    "id": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "checks": {
      +      "items": {
      +        "properties": {
      +          "advisory": {
      +            "description": "true = reported but never decides the verdict (the live did.json cross-check)",
      +            "type": "boolean"
      +          },
      +          "check": {
      +            "type": "string"
      +          },
      +          "code": {
      +            "type": "string"
      +          },
      +          "detail": {
      +            "type": "string"
      +          },
      +          "ok": {
      +            "description": "true = passed, false = failed, null = not applicable or not run (detail says UNCHECKED)",
      +            "type": [
      +              "boolean",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "family": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "id": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "not_a_certification": {
      +      "type": "boolean"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "pinned_key": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "reason": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "reasons": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "rule": {
      +      "type": "string"
      +    },
      +    "state": {
      +      "description": "VALID, INVALID or UNCHECKABLE",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "state"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "checks": {
      -      "items": {
      -        "properties": {
      -          "advisory": {
      -            "description": "true = reported but never decides the verdict (the live did.json cross-check)",
      -            "type": "boolean"
      -          },
      -          "check": {
      -            "type": "string"
      -          },
      -          "code": {
      -            "type": "string"
      -          },
      -          "detail": {
      -            "type": "string"
      -          },
      -          "ok": {
      -            "description": "true = passed, false = failed, null = not applicable or not run (detail says UNCHECKED)",
      -            "type": [
      -              "boolean",
      -              "null"
      -            ]
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "family": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "id": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "not_a_certification": {
      -      "type": "boolean"
      -    },
      -    "note": {
      -      "type": "string"
      -    },
      -    "pinned_key": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "reason": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "reasons": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "rule": {
      -      "type": "string"
      -    },
      -    "state": {
      -      "description": "VALID, INVALID or UNCHECKABLE",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "state"
      -  ],
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "checks": {
      +      "items": {
      +        "properties": {
      +          "advisory": {
      +            "description": "true = reported but never decides the verdict (the live did.json cross-check)",
      +            "type": "boolean"
      +          },
      +          "check": {
      +            "type": "string"
      +          },
      +          "code": {
      +            "type": "string"
      +          },
      +          "detail": {
      +            "type": "string"
      +          },
      +          "ok": {
      +            "description": "true = passed, false = failed, null = not applicable or not run (detail says UNCHECKED)",
      +            "type": [
      +              "boolean",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "family": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "id": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "not_a_certification": {
      +      "type": "boolean"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "pinned_key": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "reason": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "reasons": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "rule": {
      +      "type": "string"
      +    },
      +    "state": {
      +      "description": "VALID, INVALID or UNCHECKABLE",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "state"
      +  ],
      +  "type": "object"
      +}
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "checks": {
      -      "items": {
      -        "properties": {
      -          "advisory": {
      -            "description": "true = reported but never decides the verdict (the live did.json cross-check)",
      -            "type": "boolean"
      -          },
      -          "check": {
      -            "type": "string"
      -          },
      -          "code": {
      -            "type": "string"
      -          },
      -          "detail": {
      -            "type": "string"
      -          },
      -          "ok": {
      -            "description": "true = passed, false = failed, null = not applicable or not run (detail says UNCHECKED)",
      -            "type": [
      -              "boolean",
      -              "null"
      -            ]
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "family": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "id": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "not_a_certification": {
      -      "type": "boolean"
      -    },
      -    "note": {
      -      "type": "string"
      -    },
      -    "pinned_key": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "reason": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "reasons": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "rule": {
      -      "type": "string"
      -    },
      -    "state": {
      -      "description": "VALID, INVALID or UNCHECKABLE",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "state"
      -  ],
      -  "type": "object"
      -}New value: +null
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "checks": {
      +      "items": {
      +        "properties": {
      +          "advisory": {
      +            "description": "true = reported but never decides the verdict (the live did.json cross-check)",
      +            "type": "boolean"
      +          },
      +          "check": {
      +            "type": "string"
      +          },
      +          "code": {
      +            "type": "string"
      +          },
      +          "detail": {
      +            "type": "string"
      +          },
      +          "ok": {
      +            "description": "true = passed, false = failed, null = not applicable or not run (detail says UNCHECKED)",
      +            "type": [
      +              "boolean",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "family": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "id": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "not_a_certification": {
      +      "type": "boolean"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "pinned_key": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "reason": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "reasons": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "rule": {
      +      "type": "string"
      +    },
      +    "state": {
      +      "description": "VALID, INVALID or UNCHECKABLE",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "state"
      +  ],
      +  "type": "object"
      +}
  7. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/openWorld annotations by disclosing the pinned-key model, the trust distinction between inline keys and DID references, and the three-verdict outcome model (VALID/INVALID/UNCHECKABLE). This is exactly the kind of behavioral detail an agent needs to interpret results and avoid treating 'could not check' as forgery.

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?

Front-loaded with the core action and the rule link, and every clause conveys substantive information. It is a dense single block rather than cleanly segmented, which slightly hurts readability but not content economy.

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?

Output schema exists so return values need not be explained, and the description still covers verification mechanics, key trust boundaries, verdict semantics, and input resolution. Nothing an agent needs to invoke or interpret the tool 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% and the single param's anyOf forms are already documented, so the baseline is 3. The description adds meaning by tying the id form to its origin ('the record id shown on the site and the card field of list_cards') and to the resolution URL, giving context the schema alone does not.

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 a specific verb (verify) plus the exact resource (a signed gspc.measurement-card) and names the governing rule document. It is clearly distinguishable from siblings like verify_capsule and verify_inclusion by naming the artifact it checks.

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 when the tool applies (checking a signed card against a pinned key set) and enumerates the accepted input forms and the resolution behavior for a 64-hex id. It does not, however, explicitly contrast itself with the sibling verifiers or say when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.