Skip to main content
Glama
danielsimonjr

Enhanced Knowledge Graph Memory Server

by danielsimonjr
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

export_graph

Export knowledge graphs in JSON, CSV, GraphML, RDF, or other formats, with optional filters, brotli compression, and PII redaction for sharing or backup.

Instructions

Export knowledge graph in various formats with optional brotli compression and streaming for large graphs. Supports W3C Linked Data formats (turtle, rdf-xml, json-ld) added in η.5.4.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoOptional filter
formatYesExport format. W3C Linked Data: turtle (RDF 1.1 Turtle), rdf-xml (RDF 1.1 XML with Statement reification for non-NCName predicates), json-ld (JSON-LD 1.1 with @context mapping to RDFS + DCTerms).
compressNoCompress output with brotli (auto-enabled for >100KB)
redactPiiNoWhen true, scrub PII (email/SSN/credit-card/phone/IPv4) from observations before export. Uses η.6.3 PiiRedactor with default pattern bank.
streamingNoUse streaming mode to write directly to file (requires outputPath)
outputPathNoFile path for streaming export. Auto-enables streaming for graphs with >= 5000 entities.
compressionQualityNoBrotli quality level 0-11 (default: 6). Higher = better compression but slower.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv12.7.0
    • changedInput schema / properties / format / description
      Previous value: -"Export format"New value: +"Export format. W3C Linked Data: turtle (RDF 1.1 Turtle), rdf-xml (RDF 1.1 XML with Statement reification for non-NCName predicates), json-ld (JSON-LD 1.1 with @context mapping to RDFS + DCTerms)."
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "json",
-  "csv",
-  "graphml",
-  "gexf",
-  "dot",
-  "markdown",
-  "mermaid"
-]New value: +[
+  "json",
+  "csv",
+  "graphml",
+  "gexf",
+  "dot",
+  "markdown",
+  "mermaid",
+  "turtle",
+  "rdf-xml",
+  "json-ld"
+]
    • addedInput schema / properties / redactPii
      Added value: +{
+  "default": false,
+  "description": "When true, scrub PII (email/SSN/credit-card/phone/IPv4) from observations before export. Uses η.6.3 PiiRedactor with default pattern bank.",
+  "type": "boolean"
+}
  2. First observedv11.1.1

TDQS

A3.6/5.0
Behavior4/5

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

Discloses behaviors like optional brotli compression, auto-enabling for small files, streaming for large graphs, and PII redaction. Covers version notes for formats. No annotations provided, so description carries full burden.

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?

Two sentences front-loading key functionality. The second sentence adds version info which may be extraneous but does not detract significantly.

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?

Lacks description of output format or return value (no output schema). Does not mention the filter parameter. For a complex tool with 7 params, more detail on usage is needed.

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?

Schema coverage is 100% with detailed parameter descriptions. The tool description adds high-level context about compression and streaming but does not significantly extend schema semantics.

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 clearly states the tool exports a knowledge graph in various formats, listing specific W3C Linked Data formats. It uses a specific verb ('Export') and resource ('knowledge graph'), and distinguishes from sibling tools like import_graph.

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?

No guidance on when to use this tool versus alternatives (e.g., read_graph). No mention of prerequisites or context where export is appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielsimonjr/memory-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server