Skip to main content
Glama

td_memory_replay

Replay a saved technique in a new parent path: creates nodes, sets parameters and expressions, wires connections. Works with full recipes.

Instructions

Rebuild a saved technique in a new location in the TD project.

Creates nodes, sets parameters and expressions, wires connections. Only works for techniques with a full recipe (small/medium complexity).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoSkip build compatibility checks and replay anyway.
scopeNo'project' or 'global'.project
name_prefixNoOptional prefix for created node names.
parent_pathYesParent COMP path where the technique will be rebuilt.
technique_idYesID of the saved technique to replay.
recreate_rootNov1.4.7 Bug V opt-in. If True and the recipe's '/' entry has family='COMP', the replay creates that wrapper COMP under parent_path first and builds all children inside it. Default False preserves the existing flat-replay behavior where '/' is aliased to parent_path (children land as siblings). Set to True when you want a faithful clone of a COMP-wrapped technique.
param_semantics_policyNoDocs-grounded parameter safety policy for replayed recipe params. 'warn' preserves replay behavior with attached findings; 'block' refuses risky or invalid parameter writes before any live mutation.warn
Behavior3/5

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

Annotations already indicate a read-write, non-destructive action. The description adds that it creates nodes, sets params, and wires connections, which is consistent. No surprises but no extra depth beyond annotations.

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 sentences, no redundancy. The first sentence states the primary action, the second adds behavioral detail and a constraint. Efficient and front-loaded.

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 description explains the action and limitations but does not specify return values (no output schema). For a complex tool with 7 parameters, this is adequate but not fully complete.

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

Parameters3/5

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

Schema coverage is 100%; each parameter has a description. The tool description adds overall context but does not enhance individual parameter meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 states the verb 'Rebuild a saved technique' and specifies the resource and constraints (full recipe, new location). It distinguishes from sibling memory tools like save/recall by focusing on replay/rebuild.

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?

The description provides usage context: when to use (rebuilding a technique) and constraints (only for full recipe, small/medium complexity). It does not explicitly mention alternatives but the constraint helps avoid misuse.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dreamrec/TDPilot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server