Skip to main content
Glama

repo_memory_audit

Read-onlyIdempotent

Audit local and Git-shared memories to find stale or missing source evidence, so coding agents can verify context before relying on it.

Instructions

Audit local and Git-shared memories for stale or missing source evidence.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "repo_memory_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.6

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description adds the useful detail that the audit spans both local and Git-shared memories and looks for missing source evidence, but says nothing about what the audit produces or how findings are surfaced.

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?

A single sentence with no filler, front-loading the verb and the resource. Every clause (local and Git-shared scope, stale/missing evidence criteria) carries information.

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?

For a zero-parameter, read-only tool the description covers what is inspected and against what criteria, which is close to complete. The gap is the absence of an output schema combined with no indication of what the audit returns (a report, a list of flagged memories, a pass/fail), leaving the agent guessing about the result shape.

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?

The tool takes zero parameters, so the baseline is 4. The description confirms there is no scope or filter argument to consider — it audits all local and Git-shared memories — which is the relevant semantic information for a parameterless tool.

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 gives a specific verb (audit) and resource (local and Git-shared memories) plus the exact condition being checked: stale or missing source evidence. That separates it from the sibling curation tools (repo_approve_memory, repo_reject_memory, repo_stage_memory) which act on memories rather than inspect their evidence, though it does not explicitly name them.

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

Usage Guidelines3/5

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

There is no explicit when-to-use statement, no prerequisites, and no named alternative. The usage is only implied by the audit target — an agent can infer it is for checking memory trustworthiness before relying on results, but the description does not say so.

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