Planning System MCP Server

add_learning

Record a learning episode to document insights, decisions, or patterns. Automatically extracts entities and relationships, and alerts if the new content contradicts existing facts.

Instructions

Record a knowledge episode. Use after research, on decisions, or when discovering important context. Graphiti extracts entities/relationships automatically. Surfaces coherence_warnings if the new content contradicts existing facts.

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

Input Schema

Name	Required	Default
`content`	Yes
`scope`	No
`entry_type`	No	fact
`source_description`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.8.1Apr 29, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations exist, so description carries full burden. Discloses critical behaviors: content is auto-processed (entity/relationship extraction) and coherence warnings are surfaced. Does not mention error handling or permissions, but core behavioral traits are covered.

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 sentences front-loaded with main purpose, each sentence adds value. Could be slightly more structured with parameter details, but overall efficient and clear.

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?

With no annotations, no output schema, and nested parameters, description is somewhat lightweight. Covers core purpose and behavioral traits, but fails to explain return behavior or parameter usage fully. Adequate for a simple creation tool but leaves gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so description must compensate but fails to. Does not explain the meaning of 'scope' (nested object with plan_id, goal_id, node_id), 'entry_type' enum values, or 'source_description'. Only 'content' is implied but not clarified.

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?

Description starts with 'Record a knowledge episode,' clearly stating the main action. Lists specific use cases (after research, on decisions, discovering context) which differentiates it from sibling tools like recall_knowledge (retrieval) and others.

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 says when to use: after research, on decisions, or when discovering important context. Also mentions automatic entity extraction and coherence warnings, helping the agent understand context. Lacks explicit when-not-to-use or alternative tool names, but sufficient given the clear purpose.

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