Skip to main content
Glama
Sign In
wx-mp-mcp

wx-mp-mcp

by k98crypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Import existing capture

mp_capture_import

Import HAR, cURL, JSON, or JSONL captures and convert them into sign-crack-compatible JSONL without proxy capture, flattening bodies, folding GET queries, and flagging sign-field requests.

Instructions

把已有抓包归一成 sign-crack 兼容的 JSONL —— 用户自己用任意工具抓的包可直接导入，无需再走 mp_capture_* 代理。支持 HAR(Charles/Fiddler/DevTools)、cURL(DevTools 复制)、JSON 请求体、JSONL。自动扁平化 JSON 体、折入 GET query 参数，并标出带 sign 字段的请求。

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

Input Schema

NameRequiredDescriptionDefault
outNo输出 JSONL 路径 (默认 captures/imported-*.jsonl)
inputNo抓包文件路径 (HAR/cURL文本/JSON/JSONL)
formatNoauto|har|curl|json|jsonl (默认 auto 自动识别)
api_urlNo当输入是纯 JSON 请求体时，指定接口 URL
contentNo直接传抓包内容文本 (代替 input 文件)
url_filterNo只导入 URL 含此子串的请求

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add useful behavior: auto-detection of input format, automatic flattening of JSON bodies, folding of GET query parameters, flagging of requests that contain sign fields, and a default output path. It omits equally important traits for a file-writing tool: whether an existing output file is overwritten or appended, and what happens when parsing fails or a format is unrecognized.

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 dense sentences with the capability and its sibling differentiation front-loaded, followed by the supported formats and automatic transformations. No filler and no repetition of the title.

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 six-parameter, no-annotation tool with no output schema, the description covers what the tool converts, the accepted input formats, the automatic normalizations, and a default output location. Remaining gaps are overwrite/append semantics and failure behavior, which matter for a write-to-disk operation.

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%, so the schema already documents all six parameters and the baseline is 3. The description's format list (HAR/cURL/JSON/JSONL) reinforces the values of the format parameter and its auto-detect behavior, but adds no new semantics for input, content, api_url, url_filter, or out beyond what the schema properties state.

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 names a specific verb-resource pair (normalize existing captures into sign-crack-compatible JSONL), enumerates the supported inputs (HAR, including which tools produce it; cURL; JSON body; JSONL), and explicitly contrasts itself with the mp_capture_* proxy tools. An agent can tell this is the import path rather than a live capture path.

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?

The description says the user can import packets captured with any tool directly and that this avoids going through the mp_capture_* proxy, which names a real alternative family and the condition that selects it. It does not state a hard when-not case (for example, which tool to use when no file exists yet), so it falls short of a full routing statement.

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