Gravitas-Core-MCP

Overview Schema Source Related Servers Discussions Admin

memory_save_snapshot

Record a snapshot of the current task's context, capturing project map, safe-to-edit files, and do-not-touch files, to enable state persistence.

Instructions

Save a context snapshot for current task (internal use).

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": {
      "snapshot_id": "<snapshot_id>",
      "task_id": "<task_id>",
      "project_map": "<project_map>",
      "safe_to_edit": "<safe_to_edit>",
      "do_not_touch": "<do_not_touch>"
    },
    "name": "memory_save_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
`task_id`	Yes
`project_map`	Yes
`snapshot_id`	Yes
`do_not_touch`	Yes
`safe_to_edit`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Without annotations, the description carries full burden for behavioral disclosure. It only states 'save a context snapshot' but does not reveal side effects (e.g., overwriting behavior), dependencies, or idempotency. Minimal transparency is provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, very concise. However, it is so brief that it omits necessary detail, crossing from concise into underspecified. It is front-loaded but at the expense of completeness.

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

Completeness2/5

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

Given the tool's complexity (5 required params, nested objects, no output schema), the description is far too minimal. It lacks information about parameter semantics, return values, and how it interacts with other memory tools. The input schema is also undocumented, making the tool difficult to use correctly.

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

Parameters1/5

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

Schema description coverage is 0% (no parameter descriptions), and the tool description adds no meaning to the five required parameters (snapshot_id, task_id, project_map, safe_to_edit, do_not_touch). The description fails to explain their roles or constraints, leaving the agent uninformed about critical inputs.

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 the tool saves a context snapshot for the current task, specifying 'internal use' which hints at system usage. However, it does not differentiate from sibling tools like memory_set_canonical or get_canonical_state, which may have overlapping purposes.

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 explicit guidance on when to use this tool versus alternatives. The phrase 'internal use' is vague and does not provide clear usage context or exclusions. There is no mention of scenarios where this tool should not be used.

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