rhizome-mcp

Overview Schema Source Related Servers Discussions Admin

save_attempt_note

Record a restartable checkpoint, finding, warning, or progress note on an active attempt, attaching artifacts and next steps to maintain durable project memory across agent sessions.

Instructions

Append a restartable checkpoint, finding, warning, or progress note.

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": {
      "attempt_id": "<attempt_id>",
      "lease_token": "<lease_token>",
      "kind": "<kind>",
      "content": "<content>"
    },
    "name": "save_attempt_note"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	How the note should be classified.
`content`	Yes	Required restartable note content.
`artifacts`	No	Optional artifacts created or referenced by this work.
`important`	No	Marks the note as important.
`attempt_id`	Yes	Active attempt receiving the note.
`next_steps`	No	Optional concrete actions after this note.
`lease_token`	Yes	Secret proof of the active attempt lease.
`project_ref`	No	Project reference returned by open_project. Pass it explicitly for stateless routing; omit only when using a configured default.
`idempotency_key`	No	Optional key that replays the same note request.
`agent_session_handle`	No	Optional durable session handle for request attribution.

Output Schema

Name	Required	Description	Default
`artifacts`	Yes
`attempt_note`	Yes
`next_actions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv1.2.1Aug 13, 2026
- addedInput schema / properties / agent_session_handle / description
```
Added value: +"Optional durable session handle for request attribution."
```
- addedInput schema / properties / artifacts / description
```
Added value: +"Optional artifacts created or referenced by this work."
```
- addedInput schema / properties / attempt_id / description
```
Added value: +"Active attempt receiving the note."
```
- addedInput schema / properties / content / description
```
Added value: +"Required restartable note content."
```
- addedInput schema / properties / idempotency_key / description
```
Added value: +"Optional key that replays the same note request."
```
- addedInput schema / properties / important / description
```
Added value: +"Marks the note as important."
```
- addedInput schema / properties / kind / description
```
Added value: +"How the note should be classified."
```
- addedInput schema / properties / lease_token / description
```
Added value: +"Secret proof of the active attempt lease."
```
- addedInput schema / properties / next_steps / description
```
Added value: +"Optional concrete actions after this note."
```
First observedv1.2.0Aug 13, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already indicate a write operation (readOnlyHint: false) but provide no additional detail. The description adds only the ambiguous word 'restartable', which may hint at checkpointing but is not explained. It does not mention the required lease_token proof, potential side effects, or any idempotency nuances (despite the idempotency_key parameter). This leaves significant behavioral gaps.

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 a single sentence and is very concise with no filler. It front-loads the action. However, 'restartable' is unclear and might mislead; a slightly more explicit phrase like 'save an attempt note that can be used to resume work' would be both concise and clearer. Still, it earns a high score for structure.

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?

For a tool with 10 parameters including sensitive auth fields (lease_token), idempotency control, and an enum, the description is too thin. It does not explain the lease requirement, the meaning of 'restartable', or how the different note kinds should be used. The output schema exists, so return values are not necessary, but the high-level operational context is missing.

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 description coverage is 100%, so the schema itself documents all parameters with descriptions. The tool description adds no parameter-specific meaning beyond 'restartable', which does not map to any one schema field. The baseline of 3 is appropriate since the schema carries the burden.

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 ('Append'), the resource (a note to an attempt), and the scope (checkpoint, finding, warning, or progress). It distinguishes from sibling tools like add_comment or record_decision by referencing attempt-specific notes. Though 'restartable' is slightly vague, the core purpose is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., active attempt lease), when to choose 'checkpoint' vs 'progress', or situations where another tool like record_decision might be more appropriate. The description is a bare statement with no exclusions or contextual hints.

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