Skip to main content
Glama

aw1-circuit-breaker-remote

aw1_verify_tee_attestation

Read-onlyIdempotent

Cryptographically verifies an ephemeral TEE execution token against the tamper-evident SQLite governance ledger. Supports x402 per-call payment ($0.001/call in Base USDC).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "attestation_id": "<attestation_id>"
    },
    "name": "aw1_verify_tee_attestation"
  }
}

Input Schema

NameRequiredDescriptionDefault
attestation_idYesThe 24-character execution token to verify against ledger invariants

Output Schema

NameRequiredDescriptionDefault
validYesTrue if the attestation signature matches ledger records
timestampNoEpoch timestamp of seal creation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / attestation_id / description
      Previous value: -"The 24-character execution token to verify"New value: +"The 24-character execution token to verify against ledger invariants"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "timestamp": {
      +      "description": "Epoch timestamp of seal creation",
      +      "type": "integer"
      +    },
      +    "valid": {
      +      "description": "True if the attestation signature matches ledger records",
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "valid"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / attestation_id / description
      Previous value: -"Hex-encoded SHA-256 attestation digest or execution token identifier (e.g. '0x...' or 'LWA-...') to cross-reference."New value: +"The 24-character execution token to verify"
  3. Changed1 schema field changed
    • changedInput schema / properties / attestation_id / description
      Previous value: -"Attestation hash seal"New value: +"Hex-encoded SHA-256 attestation digest or execution token identifier (e.g. '0x...' or 'LWA-...') to cross-reference."
  4. Changed1 schema field changed
    • changedInput schema / properties / attestation_id / description
      Previous value: -"The 24-character execution token to verify"New value: +"Attestation hash seal"
  5. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world profile, so the safety semantics are covered structurally. The description adds genuinely new behavioral context not present in the annotations: verification happens against a tamper-evident ledger, and each call incurs an x402 payment of $0.001 in Base USDC — a material fact an agent would otherwise miss.

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?

Two sentences, both front-loaded with the highest-value information: the action and target come first, the payment model second. Nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return-value semantics need not be explained, and annotations cover the safety profile for this single-parameter read. The description covers what is verified, against what, and the cost model; the only real omission is how this fits relative to the sibling execution tool, which is a usage-guidance gap rather than a completeness one.

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%: the single attestation_id parameter is documented as a 24-character execution token verified against ledger invariants. The description adds no format, sourcing, or validation detail beyond that, so the schema is doing all the parameter work — the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb ("Cryptographically verifies") with a specific resource ("an ephemeral TEE execution token") and names the verification target ("tamper-evident SQLite governance ledger"). An agent can tell this is a verification/read operation rather than an execution one, but it never mentions the sibling aw1_execute_protected_tool, so the boundary between verifying a token and executing a protected tool must be inferred from the names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus the sibling, no prerequisite or precondition (e.g. that an attestation_id must first be obtained from an execution), and no when-not guidance. The only auxiliary information is pricing, which informs cost decisions but not tool selection.

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.

Resources