Skip to main content
Glama
Sign In
memory-manager-mcp

memory-manager-mcp

by AbdulqaderAhmed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get decisions

get_decisions

List recorded project decisions from memory, newest first, and optionally exclude superseded ones by filtering active only.

Instructions

List recorded decisions for the project (newest first).

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_decisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
activeOnlyNoExclude superseded decisions.
workspacePathNoWorkspace directory of the project. Defaults to the server working directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that results are sorted newest first, which is a behavioral trait, but it does not explicitly confirm read-only semantics, permissions, or output format. 'List' implies read-only, which adds some clarity, but more detail would be expected.

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?

A single sentence, front-loaded with the action and object. Every word earns its place, with no redundant or vague phrasing.

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

Completeness4/5

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

For a simple read tool with two optional parameters and no output schema, the description adequately covers what the tool does. It implies the return of a list of decisions, though it does not describe the structure or mention the activeOnly filter (which is in the schema). Given the low complexity, this is sufficient.

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 description coverage is 100% (both activeOnly and workspacePath are documented in the schema). The description itself adds no parameter-level detail, so it does not exceed the baseline of relying on the schema.

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?

The description uses a specific verb ('List'), names the resource ('recorded decisions'), and adds ordering ('newest first'). This clearly distinguishes it from write tools like record_decision and other memory tools, making the purpose unambiguous.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives such as record_decision or get_memory. It merely says 'for the project' without mentioning exclusions or alternative scenarios. The agent is left to infer usage from context.

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