Skip to main content
Glama

Attest the current value of a subject (signed proof)

attest

Issue a signed, third-party-verifiable proof of what memory currently holds for a subject, anchored to the audit-log head, so you can prove what was known at a specific time.

Instructions

Issue a signed, third-party-verifiable attestation of what memory currently holds for subject — 'as of now, the active value is X', anchored to the tamper-evident audit-log head. Use it to prove what was known at a point in time. Verify later with verify_receipt, or independently with export_public_key.

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": {
      "subject": "<subject>"
    },
    "name": "attest"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idNo
subjectYes
user_idNodefault
agent_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A3.8/5.0
Behavior3/5

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

Adds meaningful behavior beyond annotations by explaining that the attestation is signed, third-party-verifiable, and anchored to the tamper-evident audit-log head. However, it does not clarify the side effect of issuing an attestation, how non-idempotent repeated calls behave, or whether a durable receipt is stored, so the non-readOnly/non-idempotent hints remain only partially explained.

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 tightly structured sentences, front-loaded with the core action and followed by usage and verification guidance. The quoted example clarifies the attestation semantics without adding waste.

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

Completeness3/5

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

The output schema and annotations cover return structure and safety hints, and the description explains the high-level proof semantics. Still, for a four-parameter tool with zero schema descriptions, the lack of guidance on scope and optional parameters leaves meaningful gaps for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only explains the required `subject` parameter as the memory subject being attested. It gives no meaning for `run_id`, `user_id`, or `agent_id`, even though those defaults and scoping fields may affect what is attested.

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 and resource: issue a signed, third-party-verifiable attestation of what memory currently holds for `subject`. It also frames the meaning as a point-in-time proof, which clearly distinguishes it from read-only retrieval siblings like get_memory or recall.

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?

Explicitly says to use it "to prove what was known at a point in time" and names verify_receipt and export_public_key as later verification paths. It lacks explicit when-not-to-use guidance or comparison with related tools such as history or get_memory, but the primary use case is clear.

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