Skip to main content
Glama
Sign In
Puppeteer Debugger MCP Server

Puppeteer Debugger MCP Server

by ALIEX7664
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

analyze_memory

Analyze memory usage of a web page by taking a heap snapshot, identifying memory leaks, and optimizing JavaScript memory consumption. Optionally specify a page URL to focus analysis.

Instructions

分析内存使用情况

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

Input Schema

NameRequiredDescriptionDefault
urlNo页面 URL（可选）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states a vague action. It does not disclose if it returns data, mutates state, requires permissions, or affects performance. The behavioral impact is unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise phrase with no wasted words. It is appropriately sized for a simple tool, though slightly too minimal. Still, it earns a high score for conciseness.

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

Completeness2/5

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

Given no output schema and simple parameter, the description is incomplete. It fails to explain the purpose's scope, return value, or any caveats. The agent lacks sufficient context to use the tool effectively.

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% with one optional parameter described. Baseline is 3. Description adds nothing beyond the schema, but also does not detract. No additional meaning provided.

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 '分析内存使用情况' (analyze memory usage) clearly states a specific verb and resource. It is not a tautology and distinguishes from siblings like get_heap_snapshot (snapshot) and track_allocations (tracking). However, it lacks any additional distinction or detail.

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 usage guidelines are provided. The description does not specify when to use this tool versus siblings like get_heap_snapshot or track_allocations. The agent has no context to choose appropriately.

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