Skip to main content
Glama

RAMen Memory status

memory_status
Idempotent

Shows your RAMen memory profile, retained data, pending guesses, open items, saved threads, linked computers, and updates settings you request.

Instructions

The user's profile card (how they want answers), then how much RAMen Memory keeps, AI guesses waiting for the user's OK, open items, the saved threads and which computers are linked. With settings it changes RAMen settings.

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": "memory_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
settingsNoonly what the user asked to change: checkpoints (true or false), topics ({"health": false})

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is partially covered. The description's real addition is disclosing the dual-mode split (read status normally, mutate when settings is supplied), which resolves why readOnlyHint is false, but it says nothing about what a settings change persists, whether it is reversible, or whether confirmation is needed.

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?

Length is reasonable (~two short sentences) with no padding, but the first sentence is a comma-chained run-on listing six unrelated items, so key content such as the settings/mutation mode is buried at the end. It is compact but not front-loaded or scannable.

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

Completeness3/5

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

With one optional parameter at full schema coverage and no output schema, the description must carry the return-value burden, and it does outline the returned sections. Those outlines are vague ("how much RAMen Memory keeps," "AI guesses waiting for the user's OK") and the two modes are not clearly separated, so it is adequate but leaves the agent guessing at specifics.

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

Parameters3/5

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

Schema coverage is 100% and the schema already explains that only user-requested changes belong in settings, with checkpoint/topic examples. The description only restates that settings modifies RAMen settings, adding no syntax, format, or default-value meaning beyond the schema, so baseline 3 applies.

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 enumerates concrete content (profile card, memory volume, pending AI guesses, open items, saved threads, linked computers) and discloses a second mode that mutates settings, so it is distinguishable from siblings like recall/remember/save_thread. It never states a verb for the read mode ("returns" / "reports"), leaving the primary action implicit, and the enumeration reads more like a return-value list than a purpose statement.

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?

"With settings it changes RAMen settings" gives a usable mode-selection rule: call bare to inspect status, pass settings to modify. However, it never says when to prefer this over recall/recall_thread for inspecting memory, and gives no prerequisites or exclusions for the mutating path.

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