Skip to main content
Glama

repo_approve_memory

Idempotent

Approve a staged memory and resolve temporal conflicts so coding agents can keep task context consistent.

Instructions

Approve a staged memory and resolve temporal conflicts.

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": {
      "id": "<id>"
    },
    "name": "repo_approve_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
epistemic_statusNoVERIFIED

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.6

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, idempotent mutation. The description adds real value by disclosing a side effect beyond those annotations — that approval resolves temporal conflicts — but it never says what happens to conflicting memories, whether approval can be undone, or how it relates to the epistemic_status parameter it accepts.

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?

A single short sentence with the action front-loaded and no wasted words. It is arguably too terse for a mutation tool with an unexplained enum, but structurally it is clean.

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

Completeness1/5

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

Given a write operation, an unexplained enum parameter, no output schema, and an undisclosed conflict-resolution mechanism, the definition leaves critical gaps. An agent cannot predict the effect of epistemic_status or what approval does to conflicting memories.

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%, so the description carries the full burden, and it says nothing about either parameter. The `epistemic_status` enum (VERIFIED/ACTIVE/INFERRED, default VERIFIED) is especially opaque — the description never explains what statuses mean or why approval would set one, which is exactly the kind of guidance an agent needs.

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 names a specific verb+resource ("Approve a staged memory") plus a secondary effect ("resolve temporal conflicts"), which distinguishes it from siblings like repo_reject_memory and repo_stage_memory. It is clear enough to identify the operation, though "temporal conflicts" is unexplained jargon.

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?

The only usable hint is the word "staged," implying the memory must already be staged before approval. There is no explicit statement of when to approve versus reject, no prerequisites, and no reference to repo_reject_memory or repo_review_queue.

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