Skip to main content
Glama
Sign In
memorylens-mcp

memorylens-mcp

by MarcelRoozekrans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

analyze

Identify memory leaks, fragmentation, and excessive allocations from .NET memory snapshots. Receive severity-based findings with actionable code suggestions to fix anti-patterns.

Instructions

Analyzes a memory snapshot using built-in rules to detect leaks, fragmentation, excessive allocations, and anti-patterns. Returns findings with severity, description, and optional code suggestions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "snapshotId": "<snapshotId>"
    },
    "name": "analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterPathNoPath to 'after' snapshot for comparison
beforePathNoPath to 'before' snapshot for comparison
snapshotIdYesSnapshot ID or path to analyze
snapshotPathNoPath to snapshot file
workingDirectoryNoWorking directory for resolving relative paths

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided. Description implies read-only ('analyzes'), but does not explicitly state non-destructiveness, performance impact, or any side effects.

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, concise and front-loaded with the main action and outputs. No fluff.

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?

No output schema, but description describes return fields (severity, description, suggestions). Missing details about how comparison works given afterPath/beforePath, especially compared to sibling compare_snapshots.

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%, so baseline 3. Description adds context about 'built-in rules' and return format, but does not explain the comparison parameters (afterPath, beforePath) beyond what schema provides.

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?

Clearly states it 'Analyzes a memory snapshot' and lists specific detections (leaks, fragmentation, etc.). Distinguishes from sibling tools like list_processes, snapshot, compare_snapshots.

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?

No guidance on when to use this tool vs siblings (e.g., compare_snapshots). Does not specify prerequisites or when not to use.

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