Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Read memory mode

get_memory_mode
Read-onlyIdempotent

Reads the account's memory mode to show whether nothing is saved, only user-requested items are saved, or future-relevant details are saved.

Instructions

Read the account's memory mode: off (nothing is saved or recalled), on_request (save only what the user asks to remember) or all (save what will matter later).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_memory_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is fully covered. What the description adds is meaningful system behavior — that 'off' means nothing is saved or recalled — but it says nothing about auth requirements, caching, or what the response looks like.

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?

One sentence, front-loaded with the verb and resource, then the three possible values with parenthetical definitions. No filler and nothing redundant.

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?

There is no output schema, so the description must explain the return value — and it does, defining all three modes and their practical consequences. For a zero-parameter read of a single setting, this is complete.

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?

Zero parameters, so per baseline this scores 4; there is nothing for the description to disambiguate. The enumerated mode meanings are value semantics for the return, not inputs, and are handled well elsewhere.

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?

States a specific verb and resource ('Read the account's memory mode') and scopes it to the account level. The read/set distinction against set_memory_mode is clear from the verb, but the description never names that alternative explicitly, so sibling differentiation is left implicit.

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?

Usage is only implied: an agent can infer it should call this before deciding whether/how to persist something, especially given the 'off' mode. There is no explicit when-to-use statement, no precondition, and no pointer to set_memory_mode for changing the value.

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