Skip to main content
Glama
Sign In
wmpf-mcp

wmpf-mcp

by 852764
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

paused_info

Retrieve pause reasons, hit breakpoints, call frames, and callFrameIds during debugging of Windows WeChat Mini Programs.

Instructions

Show pause reason, hit breakpoints, call frames, and callFrameIds.

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

Input Schema

NameRequiredDescriptionDefault
include_scopesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It discloses what is shown but fails to mention side effects (none, likely read-only) or state dependencies (e.g., requires paused state), leaving agent uninformed.

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?

Description is a single sentence, highly concise. It front-loads the action and lists items efficiently, but could include parameter details without becoming verbose.

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 low complexity (1 optional param, no output schema), description is incomplete: it omits parameter semantics, preconditions (must be paused), and return value format, leaving significant gaps for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet description omits any explanation of the 'include_scopes' parameter. Agent cannot infer its meaning or effect from the description.

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?

Description uses specific verb 'Show' and lists concrete resources (pause reason, hit breakpoints, call frames, callFrameIds), clearly distinguishing this from sibling tools like 'status' or 'evaluate_on_callframe'.

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 explicit guidance on when to use this tool versus alternatives (e.g., 'status' for a simpler view), no mention of prerequisites (must be paused), and no exclusion criteria.

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