Skip to main content
Glama
Sign In
memorylens-mcp

memorylens-mcp

by MarcelRoozekrans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

compare_snapshots

Compare two .NET memory snapshots taken seconds apart to detect memory leaks. Provide a process ID to receive snapshot IDs and paths for before/after analysis.

Instructions

Takes two memory snapshots of a .NET process with a delay between them for comparison. Useful for detecting memory leaks by comparing before/after state. Provide a pid. Returns the ids and paths of both snapshots.

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

Input Schema

NameRequiredDescriptionDefault
pidNoProcess ID to snapshot
commandNoNot implemented; a process id is required
processNameNoProcess name, used only to apply the profiling exclusion list
delaySecondsNoSeconds to wait between before and after snapshots (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.1
    • changedInput schema / properties / command / description
      Previous value: -"Command to launch and snapshot"New value: +"Not implemented; a process id is required"
    • changedInput schema / properties / processName / description
      Previous value: -"Process name to snapshot"New value: +"Process name, used only to apply the profiling exclusion list"
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden and it does disclose key behavior: two snapshots, delay, and return of IDs/paths. However, it does not discuss side effects, possible failures, blocking behavior, or whether the tool is purely read-only, leaving room for unanticipated runtime behavior.

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?

Three short, purposeful sentences. The action is front-loaded, the use case is given immediately after, and the required input plus return are stated clearly with no filler.

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?

The description covers what the tool does, why to use it, an important input requirement, and what it returns. Since the schema already documents the remaining parameter details, this is sufficiently complete for a tool with these siblings, though it does not explain its relation to a single snapshot tool.

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?

Schema coverage is 100% for all 4 parameters, so the baseline is 3. The description adds value by clarifying that pid is effectively required despite being nullable/optional in the schema, and says 'with a delay between them' which aligns with delaySeconds and reinforces its role.

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 states a specific action: 'Takes two memory snapshots of a .NET process with a delay between them' and explicitly connects this to memory-leak detection. It is distinguishable from the sibling 'snapshot' tool by the two-snapshot nature, though it does not name alternatives directly.

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

Usage Guidelines4/5

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

It gives clear context: detecting memory leaks by comparing before/after state, and it tells the agent that a pid must be provided. It does not explicitly mention when not to use this tool or name a sibling alternative, so exclusions are missing.

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