Skip to main content
Glama

Add to a task's journal

note

Record new information in a task's journal to update existing work instead of filing a duplicate; for closed tasks, propose the work anew.

Instructions

Add to a task's journal, the person's tasks too, when something new turns up about existing work, instead of filing a duplicate. A closed task takes none: propose the work anew. A note inside a document is a callout (> [!NOTE]), with edit_doc.

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>",
      "body": "<body>"
    },
    "name": "note"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesWhat to record, in the Tisty language
taskYesThe task id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write, so the safety profile is covered. The description adds genuinely new behavioral context: the operation is rejected on a closed task and the agent must fall back to `propose`, and the body must be written in the "Tisty language" (documented in the schema). It does not describe the response or whether the note is appended versus merged, which keeps it below a 5.

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 then the routing rules; nothing is padding. The compressed phrasing ("the person's tasks too", "takes none") trades a little readability for brevity.

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

Completeness4/5

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

For a two-parameter mutation with no output schema and full annotation coverage, the description supplies what the structured fields cannot: the precondition about closed tasks and the sibling routing for document notes. Only the success behavior/return value is left unstated, a minor gap given no output schema exists.

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 both parameters (task id and body) are already documented in the schema. The description adds no extra detail about id formats, body length limits, or formatting beyond what the schema supplies, so the baseline of 3 applies.

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

Purpose4/5

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

The opening clause gives a specific verb and resource ("Add to a task's journal"), and the closing sentence carves out a distinct case (document notes are callouts via `edit_doc`). The elliptical phrase "the person's tasks too" is not fully parseable without prior knowledge of the domain, so the scope is slightly less crisp than it could be.

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

Usage Guidelines5/5

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

It states the triggering condition ("when something new turns up about existing work") and the alternative it replaces ("instead of filing a duplicate"). It also names two exclusions with their correct substitutes: a closed task must be handled with `propose`, and a note inside a document belongs to `edit_doc`.

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