Skip to main content
Glama

task_memo_add

Add a memo to a task to track progress, record decisions, or mark issues, with optional memo types and replacement of outdated entries.

Instructions

Add a memo record to a task — for tracking progress, recording decisions, marking issues.

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_id": "<task_id>",
      "content": "<content>"
    },
    "name": "task_memo_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
authorNoAuthor name, default "leader"leader
contentYesMemo content
task_idYesTask ID
memo_typeNoType, one of "progress" / "decision" / "issue" / "summary"progress
supersedesNoOptional memo ID this entry replaces; the old memo is marked invalid (Zep invalidation semantics, no deletion)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.2

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full burden, yet it only says "add" with no disclosure of mutation effects, permissions, or append-only behavior. The important invalidation behavior (supersedes marks the old memo invalid without deleting it) appears in the schema, not the description, so the description adds little behavioral context.

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?

A single front-loaded sentence with the verb and resource first and purpose trailing. It is efficient with no wasted clauses, though "memo record" is mildly redundant.

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

Completeness5/5

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

The tool is a simple task-scoped create with a fully documented schema and an output schema, so return values need no explanation. The description covers the essential who/what, and the invalidation semantics live in the parameter description where the agent will read them.

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 baseline of 3 applies. The description's mention of progress/decisions/issues loosely echoes the memo_type enum but adds no syntax, defaults, or meaning beyond what the schema already documents for every parameter.

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?

States a specific verb and resource ("Add a memo record to a task") plus the intent behind it — progress tracking, decision recording, issue marking. An agent can tell this writes a task-scoped memo, though it does not explicitly distinguish itself from siblings like memory_add or briefing_add.

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

Usage Guidelines3/5

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

The listed purposes (progress, decisions, issues) implicitly map to the memo_type values and hint at when to use each. However, there is no explicit guidance on when to choose this over memory_add or briefing_add, and no prerequisites or exclusions.

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

Deploy Server

Other Tools