Skip to main content
Glama
CWNApps

Trust Gate MCP

by CWNApps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

verify_receipt

Checks a Trust Gate receipt offline to confirm it is unchanged, signed, key-consistent, and post-quantum verified; pin the signer with expected_kid.

Instructions

Verify a Trust Gate receipt from the certificate alone (offline). ok=true means unchanged since signing, signed, kid consistent with the embedded key, and (require_pq default on) at least one post-quantum leg verified; unsigned receipts fail. It does not prove who signed: pass expected_kid to pin the signer's Ed25519 key; a pin counts only when that key's own signature verifies (see signer_pinned). The post-quantum keys in a receipt are not covered by the kid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
receiptYes
require_pqNo
expected_kidNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / expected_kid
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Expected Kid"
+}
  2. First observedv0.2.1

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the behavioral burden. It explains what ok=true means, that unsigned receipts fail, that it does not prove signer identity, how expected_kid pinning works, and that post-quantum keys are not covered by the kid.

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 description is front-loaded with the core verification contract, then adds the important signer-pinning caveat and PQ-key caveat. Every sentence adds necessary semantic information without filler.

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 cryptographic complexity, missing annotations, and 0% schema description coverage, the description covers the critical behavioral guarantees and limitations. Return values are additionally covered by the output schema.

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 description coverage is 0%, so the description must compensate. It explains require_pq's effective default and expected_kid's pinning semantics in detail, though the receipt parameter itself is left largely opaque as a Trust Gate receipt object.

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 states a specific verb and resource: verify a Trust Gate receipt. It also names the exact verification mode, offline from the certificate alone, which clearly distinguishes it from the minting siblings.

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?

It gives clear context for use and conditionally describes when to supply expected_kid to pin the signer. It does not explicitly compare against sibling tools or state when not to use this tool, so it falls short of the top level.

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

Deploy Server

Other Tools