Skip to main content
Glama
Sign In
Ruishu MCP

Ruishu MCP

by markx520
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Intercepted Traffic

get_intercepted_traffic
Read-only

Retrieve decrypted, normalized JSON network traffic logs. Filter by URL keyword, request/response type, or newest record count to inspect captured browser traffic and reduce token usage.

Instructions

Step 2: Data Observation. Retrieves decrypted and normalized JSON network traffic logs processed by the data pipeline. Supports URL keyword filtering and data type slicing to drastically reduce token usage.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of newest records to retrieve (prevents context explosion), retrieves all if not provided.
sub_typeNoFilter by packet category: 'all', 'request', or 'response' (default: 'all')
filter_keywordNoFilter traffic by URL keyword or path substring (e.g. '/api/query') to save tokens

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context that the data is decrypted, normalized, and pipeline-processed, but it says nothing about ordering, pagination, or what happens when no traffic has been captured. With annotations carrying the safety burden, this is adequate but not rich.

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?

Two sentences, front-loaded with the workflow step and the core action, with no filler. The token-usage rationale is a useful justification rather than padding.

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?

There is no output schema, so the description must convey the return shape, and it does: decrypted, normalized JSON traffic logs. Combined with full schema coverage and annotations, an agent has enough to call it correctly; only edge-case behavior (empty results, ordering) is unstated.

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 all three parameters are already documented in the schema, which sets the baseline at 3. The description reinforces the intent of filter_keyword and sub_type by framing them as token-saving slicing, but adds no syntax or format detail beyond the schema.

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 names a specific verb and resource: it 'retrieves decrypted and normalized JSON network traffic logs processed by the data pipeline.' That is concrete enough for an agent to know it is the data-retrieval step, and the 'Step 2: Data Observation' label places it in a workflow. It does not explicitly contrast itself with the sibling tools, but those siblings (navigate_to, execute_page_action, check_ruishu_status) are clearly different in kind.

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

Usage Guidelines3/5

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

The 'Step 2' framing implies when in the workflow to call it, and the mention of filtering to 'drastically reduce token usage' hints at how to call it efficiently. However, there is no explicit when-not guidance, no statement of prerequisites (for example, that interception must be initialized first), and no named alternative.

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