server-memory

Overview Schema Source Related Servers Discussions Admin

import_graph

Import knowledge graph data from JSON or JSONL files, automatically skipping duplicate entities and relations referencing missing entities.

Instructions

Import knowledge graph data. Auto-detects JSON or JSONL format.

Compatible with old @modelcontextprotocol/server-memory JSONL files. Skips duplicate entities. Skips relations to missing entities.

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": {
      "data": "<data>"
    },
    "name": "import_graph"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 14, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses auto-format detection, compatibility, and skip behaviors (duplicates, missing entities). However, it does not mention whether the import is destructive (overwrites), what happens on error, or return value details (output schema exists but not described).

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 very concise, with two short paragraphs. All sentences add value: main purpose first, then compatibility and behaviors. No wasted words.

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?

Given the tool's complexity (import with auto-format detection, skip logic) and the lack of annotations or parameter descriptions, the description covers key behaviors but misses details like expected data structure, success/error handling, and performance implications. Output schema exists, so return value documentation is not required, but more context would be helpful.

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

Parameters3/5

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

With 0% schema description coverage, the description adds some meaning by stating the data parameter expects JSON or JSONL format. But it does not specify the expected structure (e.g., entities and relations array) or provide examples, leaving ambiguity.

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?

The description clearly states it imports knowledge graph data and specifies auto-detection of JSON/JSONL formats. It also mentions compatibility and skip behaviors. However, it does not explicitly differentiate from sibling tools like create_entities, which also creates entities but individually.

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?

The description provides context about compatibility with old server-memory files and mentions skip behaviors, implying usage. But it lacks explicit when-to-use/when-not-to-use guidance and does not name alternatives like create_entities for bulk vs individual imports.

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