SecondBrain

memory_update

Append a dated section to an existing Markdown note, recording new content while preserving the original. Optionally include a heading for the new entry.

Instructions

Safely append a dated section to an existing Markdown note in SecondBrain.

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": {
      "path": "<path>",
      "content": "<content>"
    },
    "name": "memory_update"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`content`	Yes
`heading`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It claims 'safely' appends but does not explain what 'safely' entails, what happens if the note does not exist, whether the note is created or modified, or any permission or format requirements. The behavioral disclosure is minimal and vague.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence that front-loads the core action and context. Every word contributes value, and there is no redundant or filler content.

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 mutation tool with no annotations, no output schema, and three parameters, the one-sentence description is insufficient. It does not explain note identification, content format, heading semantics, error conditions, or how this tool behaves relative to its many siblings. The overall context is under-specified for reliable agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. The description does not mention the parameters (path, content, heading) or explain how they map to the append operation. The parameter names are vaguely self-explanatory, but there is no clarification of what 'dated section' means in relation to the heading parameter or how content should be formatted. The description fails to compensate for the schema's lack of parameter details.

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 action ('append'), the target ('existing Markdown note'), and the context ('SecondBrain'). It distinguishes from siblings by emphasizing the append/update operation, which contrasts with search/get/capture/rebuild tools.

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 explicit guidance on when to use this tool versus alternatives like memory_capture or memory_rebuild. The implied use case (appending dated sections) is present, but there are no when-to-use or when-not-to-use instructions, nor any mention of sibling tools.

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

Deploy Server