Skip to main content
Glama

verify_memory

Promote a confirmed candidate memory to trusted/committed so it can enter high-authority context again, or demote it back to candidate when it is no longer verified.

Instructions

Promote an UNVERIFIED (candidate) memory to trusted/committed after you have confirmed its content is a legitimate fact. Once verified, it can inject into high-authority context again. Use this to resolve the candidate/committed boundary in-session (the operator does not do it manually). Pass verified=false to demote a memory back to candidate.

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": {
      "slug": "<slug>"
    },
    "name": "verify_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSlug of the memory to (un)verify.
verifiedNotrue = promote to trusted (default); false = demote back to candidate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.14.3

TDQS

A4.6/5.0
Behavior4/5

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

Despite having no annotations, the description is highly behavioral by explaining the consequence of verification, namely that the memory 'can inject into high-authority context again.' This reveals a critical operational side effect of the verification process.

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?

The description is dense but well-organized, progressing logically from the primary goal to the technical operation (boundary resolution) and the explicit use case for demotion. All sentences contribute to the tool's unique operational context.

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 complexity of memory lifecycle management, the description is highly complete. It covers the scope, the outcome of verification (high-authority injection), the limitation of the operator, and the two primary modes of operation (promote/demote).

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?

Although schema coverage is 100%, the description adds significant value by explaining the functional meaning of the `verified` parameter. Specifically, it clarifies that passing `false` is the instruction to demote the memory back to its candidate state, giving that boolean semantic depth beyond the schema's simple description.

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 clearly defines the action (promote/demote) and the resource (unverified memory), immediately distinguishing it from retrieval siblings like get_memory. It identifies the tool's core function as managing the candidate/committed status.

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

Usage Guidelines5/5

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

It provides comprehensive guidance by explaining the specific conditions for use—confirmating content is a legitimate fact. Furthermore, it instructs the agent on the inverse usage: passing verified=false to demote the memory back to a candidate state.

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