Skip to main content
Glama

Rewrite a note in a task's journal

reword_note
DestructiveIdempotent

Rewrite an existing note in a task journal by replacing its full body, using the task ID and note ID from read. Use this to correct or update a note without adding a new one.

Instructions

Rewrite a note in the journal of an open task, named by the id read shows beside it. The new body replaces it whole and cannot be empty. To add one, 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": {
      "task": "<task>",
      "note": "<note>",
      "body": "<body>"
    },
    "name": "reword_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesWhat the note says now, in the Tisty language
noteYesThe note's id, from `read`
taskYesThe task id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.43.2
    • changedInput schema / properties / note / description
      Previous value: -"The note's id, from `read` with `journal`"New value: +"The note's id, from `read`"
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the bar is lower. The description still adds real value by stating the new body replaces the note whole and cannot be empty, which tells the agent the prior content is fully lost. It says nothing about error behavior when the note id is stale or about whether a rewrite is recoverable.

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?

Three short sentences, front-loaded with the action and ending with the sibling pointer. The phrase 'named by the id `read` shows beside it' is slightly awkward but carries real disambiguation value, so nothing is wasted.

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?

A destructive, idempotent mutation whose parameters are fully documented by schema, so the definition covers the essentials. Missing is any note on failure modes (unknown note id, closed task) or recoverability, which matter for an operation that overwrites content whole.

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%, so the schema already defines task, note, and body. The description adds a semantic constraint on body (full replacement, non-empty) that the schema does not carry, but nothing beyond that. Baseline 3 applies.

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?

States a specific verb and resource ('Rewrite a note in the journal of an open task') plus the scoping rule that the note is identified by the id `read` shows. It also names the sibling that creates notes, so the agent can tell reword from add without consulting schemas.

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?

Explicitly routes the agent to `note` when the intent is to add rather than rewrite, and the word 'open' implicitly excludes tasks that are not open. No exclusion is given relative to other rewrite tools such as reword_step, so the guidance is clear but not exhaustive.

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