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

memory-manager-mcp

by AbdulqaderAhmed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Start session

start_session

Start tracking an agent working session for a project, enabling persistent memory and context sharing across clients. Call when beginning work.

Instructions

Start tracking an agent working session for the project. Call when beginning work; call finish_session when done.

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

Input Schema

NameRequiredDescriptionDefault
agentIdNoIdentifier of the calling agent/client, e.g. "cursor", "vscode", "claude-cli".
agentNameNoHuman-friendly client name, e.g. "Cursor".
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

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It communicates that a session begins and is tracked, and implies persistence until finish_session, but does not disclose side effects, idempotency, prerequisites (e.g., whether a project context must already exist), or behavior when a session is already active. Basic transparency is present, but richer details are missing.

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?

Two sentences, front-loaded with the core action, and every word earns its place. It avoids redundancy and clearly communicates the essential purpose and usage in a compact form.

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, low-complexity tool with fully documented schema and no output schema, the description is nearly sufficient. It explains what the tool does and when to use it, though it could add a brief note on prerequisites or idempotency. Given the simplicity, this is a minor gap rather than a major omission.

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%; all three optional parameters (agentId, agentName, workspacePath) have clear descriptions in the schema. The tool description adds no additional semantic value to the parameters, so baseline 3 is appropriate.

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 clearly states the tool's purpose with a specific verb ('Start tracking') and resource ('an agent working session for the project'). It also distinguishes itself from the sibling tool 'finish_session' by explicitly saying 'call finish_session when done', making the opposite action clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance ('Call when beginning work') and names the complementary tool to use at the end ('call finish_session when done'). This gives the agent clear direction on the session lifecycle and the primary alternative.

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