Skip to main content
Glama
putervision

state-memory-mcp

by putervision
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

manage_data

Destructive

Export and import graphs, issues, trajectories, and multimodal synergy metrics for bulk data transfer or AI training datasets.

Instructions

Export and import graph structures, issue tracker items, fine-tuning trajectories, and multimodal synergy metrics (actions: export_graph, export_issues, export_trajectories, export_joint_trajectories, export_synergy_metrics, from_tick, import_graph, import_issues, import_spec). Use manage_data instead of query_graph when bulk-transferring graph data or generating AI training datasets.

Returns serialized graph payload, trajectory dataset, synergy metrics, or import statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
edgesNoArray of edge objects for import_graph.
forceNoForce overwrite during import.
limitNoMaximum items to export (1-1000).
nodesNoArray of node objects for import_graph.
sinceNoStart timestamp for trajectories.
untilNoEnd timestamp for trajectories.
actionYesThe data export or import action to execute: export_graph, export_issues, export_trajectories, export_joint_trajectories, export_synergy_metrics, from_tick, import_graph, import_issues, import_spec.
formatNoData format.
issuesNoArray of issue objects for import_issues.
offsetNoOffset for trajectories.
projectNoTarget project name or slug.
file_pathNoFile path for import_spec.
session_idNoSession ID filter for trajectories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.0
    • changedInput schema / properties / action / description
      Previous value: -"The data export or import action to execute: export_graph, export_issues, export_trajectories, export_joint_trajectories, export_synergy_metrics, import_graph, import_issues, import_spec."New value: +"The data export or import action to execute: export_graph, export_issues, export_trajectories, export_joint_trajectories, export_synergy_metrics, from_tick, import_graph, import_issues, import_spec."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "export_graph",
-  "export_issues",
-  "export_trajectories",
-  "export_joint_trajectories",
-  "export_synergy_metrics",
-  "import_graph",
-  "import_issues",
-  "import_spec"
-]New value: +[
+  "export_graph",
+  "export_issues",
+  "export_trajectories",
+  "export_joint_trajectories",
+  "export_synergy_metrics",
+  "from_tick",
+  "import_graph",
+  "import_issues",
+  "import_spec"
+]
  2. Changed2 schema fields changedv1.3.1
    • changedInput schema / properties / action / description
      Previous value: -"The data export or import action to execute."New value: +"The data export or import action to execute: export_graph, export_issues, export_trajectories, export_joint_trajectories, export_synergy_metrics, import_graph, import_issues, import_spec."
    • addedInput schema / properties / action / enum
      Added value: +[
+  "export_graph",
+  "export_issues",
+  "export_trajectories",
+  "export_joint_trajectories",
+  "export_synergy_metrics",
+  "import_graph",
+  "import_issues",
+  "import_spec"
+]
  3. Changed6 schema fields changedv1.2.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -true
    • removedInput schema / properties / edges / items / additionalProperties
      Removed value: -{}
    • removedInput schema / properties / issues / items / additionalProperties
      Removed value: -{}
    • removedInput schema / properties / nodes / items / additionalProperties
      Removed value: -{}
    • addedInput schema / required
      Added value: +[
+  "action"
+]
  4. Addedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the destructive/import consequences are partly carried by structured metadata. The description adds the return payload types (serialized graph, trajectory dataset, synergy metrics, import statistics), which is useful, but it never states that import actions can overwrite or destroy existing data — a notable omission for a destructive tool.

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 tight sentences: the first front-loads the resource scope and action list, the second routes the agent away from query_graph, and a third short sentence covers return values. Dense but every sentence earns its place; the action enumeration is long yet necessary for a nine-action tool.

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?

With 13 parameters, 100% schema coverage, and no output schema, the description sensibly supplies the return-value summary the output schema lacks and states the resource scope. It is complete enough to call correctly, though it leaves per-action parameter applicability to the schema descriptions.

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 description coverage is 100%, so the baseline is 3. The description only restates the action names already enumerated in the action enum and adds no syntax, format, or applicability guidance beyond what the schema documents (e.g., 'edges for import_graph').

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 gives specific verbs (export, import) and enumerates the four resource families (graph structures, issue tracker items, fine-tuning trajectories, synergy metrics) plus the full action list. It clearly differentiates from query_graph. It loses a point only because the tool is a broad nine-action facade whose scope is hard to hold in mind from prose alone.

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?

It explicitly names the alternative (query_graph) and the condition that selects this tool instead: bulk-transferring graph data or generating AI training datasets. It does not address the other import/export-adjacent siblings (manage_specs, manage_snapshots), so the 'when not' coverage is partial.

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

Deploy Server

Other Tools