Plain Text Memory MCP

Overview Schema Source Related Servers Discussions Admin

Export taxonomy

export_taxonomy

Idempotent

Writes the repo's memory taxonomy to a readable JSONC file beside the memory file, including schema, usage stats, and comments. Returns file path, version, and entry counts.

Instructions

Write this repo's memory taxonomy to a JSONC file the user can read.

The file sits beside the memory file as memory.local.taxonomy.jsonc. It holds the server's versioned schema (record types, tools, allowed values, resources, prompts) and this repo's usage: entry counts, entity and relation types in use, and entries per agent. Comments explain each section and the purpose of each record type. Returns the file path, the taxonomy version, and entry counts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes
`counts`	Yes
`taxonomy_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false). The description goes beyond them by disclosing the side-effect target (memory.local.taxonomy.jsonc beside the memory file), the file's contents (versioned schema, usage counts, comments), and the return values, which is real added context for a write operation.

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?

The core action and output file are front-loaded in the first sentence, and the following sentences add necessary detail about contents and return values. Slightly verbose with the multi-line breakdown of file contents, but every element is informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations carrying the safety profile, the description is more than complete: it explains the file location, what the file contains, and even summarizes the return values. Nothing an agent needs to invoke this correctly is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies the tool operates implicitly on 'this repo' with no required input.

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 opens with a specific verb and resource: 'Write this repo's memory taxonomy to a JSONC file.' It names the exact artifact produced and where it lives, and no sibling tool does anything comparable, so an agent can identify it instantly.

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?

Usage is only implied ('a JSONC file the user can read') – the description never states when to prefer this over siblings like read_graph or search_nodes, nor any trigger condition. It is adequate because the purpose makes the context fairly obvious, but no explicit guidance is given.

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

Deploy Server