Skip to main content
Glama

memory_promote

Convert high-confidence, well-evidenced memories into durable project rules. Preview candidates in dry-run mode, then confirm the write to update claude-rules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yesNoConfirm write. Without this or dry_run=false the command stays in dry-run mode.
limitNoMax candidates to return/apply (default 20).
targetNoPromotion target. Only claude-rules is implemented in PR 4 v1.
dry_runNoIf true (default), return candidates without writing. Pair with yes=true to actually write.
project_dirNoAbsolute path to the project root where .claude/rules/ should be created. Defaults to process.cwd().
min_evidenceNoMinimum supporting episode count (default 2).
min_confidenceNoMinimum memory confidence for promotion (default 0.7 for procedural, 0.8 for semantic).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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