server-memory

by MK-986123

Overview Schema Source Related Servers Discussions Admin

Python

Local

export_graph

Export the entire knowledge graph as JSON or JSONL for backup or migration.

Instructions

Export the full knowledge graph.

format: 'json' or 'jsonl' (compatible with old @modelcontextprotocol/server-memory).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_graph"
  }
}

Input Schema

Name	Required	Description	Default
`format`	No		json

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations provided; description carries full burden. States it exports data, but fails to disclose if it is read-only, any side effects, or performance implications.

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?

Two sentences with no wasted words. Front-loaded with the core action, then provides format detail.

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?

Output schema exists, so return values are partially covered. However, the description omits details on what the export returns (e.g., file, stream, data structure) and any size/performance considerations.

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

Parameters4/5

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

Schema has 0% description coverage for the 'format' parameter, but the description explains valid values ('json' or 'jsonl') and their compatibility, adding necessary context.

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?

Clearly states 'Export the full knowledge graph,' specifying verb and resource. Distinguishes from sibling 'import_graph' and 'read_graph' by implying full export, but could be more specific about the action.

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?

Mentions compatibility with old server-memory, but does not explicitly state when to use this vs. siblings like 'read_graph' or when not to use it.

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