Skip to main content
Glama

trw_init

Create a run directory and register it as the active run for starting new tasks, sprints, or investigations that need persistent TRW state.

Instructions

Create a run directory and register it as the active run.

Use when:

  • Starting a new task, sprint, or investigation that needs persistent TRW state.

  • You need run metadata, framework assets, and active-run pinning before work begins.

Bootstraps state, run metadata, events, framework assets, optional wave/artifact metadata, and a trace/profile-aware task_profile.

Input: task_name plus optional objective, config_overrides, task_root, wave_manifest, complexity signals, artifacts, and protection flag.

Output: dict with run_id, run_path, task_dir, phase, and status fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_typeNoimplementation
artifactsNo
objectiveNo
prd_scopeNo
protectedNo
task_nameNo
task_rootNo
task_typeNo
planning_modeNo
wave_manifestNo
complexity_hintNo
config_overridesNo
complexity_signalsNo
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions creating, registering, bootstrapping state, metadata, events, and assets, but lacks details on side effects, failure modes, or required permissions. Adequate but not comprehensive.

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 structured with a lead sentence and bullet points. It is reasonably concise, though some redundancy exists. The bullet list improves readability without excessive length.

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

Completeness2/5

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

Given the tool's complexity (13 params, no output schema, no annotations), the description is incomplete. It briefly mentions output fields but doesn't explain their semantics, error conditions, or preconditions. More detail is needed for an initialization tool.

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?

The input schema has 13 parameters with 0% description coverage. The description lists some parameters (task_name, objective, config_overrides, etc.) but omits others like run_type, task_type, planning_mode, and doesn't explain their meanings or formats. This leaves significant gaps.

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 states 'Create a run directory and register it as the active run' with a clear verb and resource. It lists specific actions like bootstrapping state, run metadata, etc., distinguishing it from sibling tools like trw_adopt_run.

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 'Use when' bullet points provide clear context: starting a new task, sprint, investigation needing persistent state. While it doesn't explicitly state when not to use or name alternatives, the guidance is sufficient for typical use cases.

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/wallter/trw-mcp'

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