Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Set memory mode

set_memory_mode
DestructiveIdempotent

Set the account's memory mode to off, on_request, or all when a user requests a change, controlling when memory is used.

Instructions

Set the account's memory mode when the user asks: off, on_request or all.

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": {
      "memory_mode": "<memory_mode>"
    },
    "name": "set_memory_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
memory_modeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds only the account-wide scope ('the account's') and says nothing about what the destructive flag means here, whether existing memories are affected, or how the three modes change the behavior of sibling memory tools.

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?

A single front-loaded sentence with no filler; the verb and scope come first and the enum follows. The 'when the user asks:' phrasing is slightly awkward but does not waste space.

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?

This is a destructive, account-wide settings mutation with three opaque enum values and no output schema. The description should explain what the modes do and what side effects occur; instead it leaves the agent guessing about the impact of a destructive operation.

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?

Schema description coverage is 0%, so the description must carry the meaning of memory_mode. It merely repeats the enum values from the schema ('off, on_request or all') without explaining what each mode does — an agent cannot tell whether 'off' disables storage entirely or just automatic capture. The one thing that matters most is left undefined.

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 names a specific verb ('Set') and resource ('the account's memory mode') and enumerates the three accepted values, so the agent knows exactly what operation is performed. It does not explicitly contrast with get_memory_mode, but the verb/resource pairing makes the distinction obvious.

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?

'when the user asks' is a trigger condition, implying the agent should only call this on explicit user request rather than proactively. There is no guidance on when to use it versus get_memory_mode, no prerequisites, and critically no indication of which mode an agent should choose in a given situation.

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