SecondBrain

memory_candidate_create

Creates an idempotent review candidate for proposed memory without altering canonical Markdown, letting you stage and vet new knowledge before it is committed.

Instructions

Create an idempotent review candidate without changing canonical Markdown.

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": {
      "source_kind": "<source_kind>",
      "source_ref": "<source_ref>",
      "source_message_ids": "<source_message_ids>",
      "source_author_type": "<source_author_type>",
      "content": "<content>",
      "memory_type": "<memory_type>",
      "scope": "<scope>",
      "confidence": "<confidence>",
      "sensitivity": "<sensitivity>",
      "proposed_target_note": "<proposed_target_note>"
    },
    "name": "memory_candidate_create"
  }
}

Input Schema

Name	Required	Default
`scope`	Yes
`content`	Yes
`audience`	No
`confidence`	Yes
`expires_at`	No
`source_ref`	Yes
`supersedes`	No
`memory_type`	Yes
`sensitivity`	Yes
`source_kind`	Yes
`memory_level`	No	L1
`conflicts_with`	No
`injection_mode`	No	tool
`source_author_type`	Yes
`source_message_ids`	Yes
`proposed_target_note`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.0Oct 21, 2026

TDQS

C2.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two genuinely useful behaviors: the operation is idempotent (retry-safe) and it does not mutate canonical Markdown. However, it omits what happens on validation failure, how sensitivity='prohibited' is handled, permission requirements, and whether duplicates are deduplicated or merely tolerated.

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 zero filler, which is efficient. Given the 16-parameter surface, however, the extreme terseness borders on under-specification rather than disciplined conciseness.

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 16-parameter (10 required) creation tool with no annotations, no output schema, and no parameter documentation, one sentence is not enough. The agent lacks guidance on field semantics, idempotency key behavior, and error conditions, all of which matter before invoking a write operation.

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?

The schema has 16 parameters with 0% description coverage, and the description mentions none of them. Required fields like source_kind, memory_type, proposed_target_note, and the sensitivity/scope enums are entirely unexplained, forcing the agent to guess at accepted formats and semantics.

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 ('Create') and resource ('review candidate'), and the clause 'without changing canonical Markdown' separates it from mutating siblings like memory_update. The term 'review candidate' is domain jargon left unexplained, but the sibling set (memory_candidate_approve/reject/expire) makes the intent inferable.

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?

There is no explicit when-to-use or when-not-to-use guidance. The phrase 'without changing canonical Markdown' implicitly contrasts with memory_update, but the agent must infer that this is the staging step preceding memory_candidate_approve. No prerequisites, sequencing, or alternatives are named.

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

Deploy Server