Skip to main content
Glama
Sign In
Gravitas-Core-MCP

Gravitas-Core-MCP

by ahmed-coding
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_set_canonical

Set a verified snapshot as the canonical immutable state to create a permanent, unchangeable reference for a project.

Instructions

Set the canonical (immutable) state to a snapshot (after verification).

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>"
    },
    "name": "memory_set_canonical"
  }
}

Input Schema

NameRequiredDescriptionDefault
snapshot_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It mentions setting an 'immutable' state, implying finality, but fails to explain what happens to the previous canonical state, if the operation is reversible, or any side effects. The term 'set' contradicts 'immutable' without clarification.

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 description is a single sentence with minimal waste. However, it could benefit from additional context without becoming verbose.

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?

The tool is simple but part of a workflow with siblings like 'memory_save_snapshot' and 'get_canonical_state'. The description lacks prerequisites (e.g., the snapshot must exist and be verified) and does not explain the role of this tool in the broader context, leaving gaps for a new user.

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

Parameters2/5

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

With 0% schema description coverage, the parameter 'snapshot_id' is entirely undocumented. The description adds only that it refers to a 'snapshot', but does not specify its origin, format, or how to obtain it, leaving the agent guessing.

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 verb 'Set' and the resource 'canonical (immutable) state', with an implied workflow step 'after verification'. It distinguishes from siblings like 'get_canonical_state' by indicating mutation, but does not explicitly contrast with 'memory_save_snapshot' or other state-changing tools.

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 like 'memory_save_snapshot'. The phrase 'after verification' hints at a prerequisite but does not elaborate on conditions or scenarios.

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