On Board

Overview Schema Source Related Servers Discussions Admin

memory_init

Idempotent

Create .agent-mem/ to initialize shared project memory for AI agents and IDEs, ensuring context continuity. Call once per project; safe to re-call.

Instructions

Initialize .agent-mem/ in the project root. Call once per project. Safe to re-call.

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": {
      "params": "<params>"
    },
    "name": "memory_init"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.0.4Aug 3, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description adds the key behavioral fact that it initializes .agent-mem/ in the project root and reinforces idempotency with 'Safe to re-call'. Annotations already convey idempotentHint=true and destructiveHint=false, so the description aligns but doesn't significantly extend beyond them, lacking details like overwrite behavior or prerequisites.

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 three short sentences, front-loaded with the primary action. Each sentence adds value—purpose, when to call, and re-call safety—with no wasted words.

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?

The tool is simple, has an output schema, and strong annotations. The description sufficiently covers purpose and usage, and the schema covers parameters. It lacks some context about what .agent-mem is used for, but that doesn't hinder invocation, so it's nearly complete.

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 description contains zero information about the required 'description' parameter or the optional 'tech_stack' parameter. With schema description coverage at 0%, the description fails to compensate, leaving parameter meaning entirely to the input schema's own field descriptions.

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 uses the specific verb 'Initialize' and identifies the exact resource '.agent-mem/' in the project root. This clearly distinguishes it from sibling read/write/search tools and establishes a unique purpose.

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?

The description provides explicit usage guidance with 'Call once per project' and 'Safe to re-call', covering when to call and idempotency. It does not name alternatives, but no close alternative exists for initialization, so this is adequate.

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