Skip to main content
Glama

ctxstore — memory that follows you across models

Ghost Mode

ghost_mode
Idempotent

Enable or disable ghost mode for this session. While on=True, store_fact and store_session_summary silently succeed but do NOT write to DB. search_facts, load_context, and search_context always work normally. Ghost mode resets to off on MCP session reconnect (not persisted).

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": {
      "on": "<on>"
    },
    "name": "ghost_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYesTrue to enable ghost mode, False to disable

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false; the description adds substantial behavior beyond that: writes silently succeed but are discarded, read tools are unaffected, state is not persisted and resets on MCP reconnect. The silent-no-op semantics are exactly the non-obvious trait an agent needs before toggling this on.

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

Conciseness5/5

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

Four short sentences, front-loaded with the action, then the effect, then the unaffected tools, then the persistence caveat. No filler and no repetition of the title.

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?

For a one-parameter session toggle with no output schema, the description covers everything material: what changes, what does not, and the lifetime of the setting. Nothing an agent needs in order to invoke it 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?

Schema coverage is 100% for the single boolean, so the schema already documents the parameter type. The description still adds meaning by spelling out the consequence of on=True (silent no-op writes) rather than just restating the flag, which goes slightly beyond the schema baseline.

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?

States a specific verb (enable/disable) and resource (ghost mode) scoped to the session, then immediately defines what the coined term means by naming the exact tools affected (store_fact, store_session_summary) and the ones unaffected. An agent can distinguish this from sibling tools without opening the schema.

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?

The description gives clear operational context — ghost mode suppresses DB writes for store_fact and store_session_summary while search/load paths behave normally — which lets an agent infer when to toggle it. It stops short of an explicit 'use this when you want to rehearse writes without persisting' recommendation or any when-not guidance, so it is clear but not fully prescriptive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.