Ruishu MCP

Get Intercepted Traffic

get_intercepted_traffic

Read-only

Retrieve merged high-fidelity JSON logs of intercepted network traffic, and clear the memory queue to prevent overflow.

Instructions

Step 2: Data Observation. Retrieves the merged high-fidelity JSON log datasets processed by the data pipeline. Automatically consumes and clears the atomic memory queue to prevent overflow.

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

Name	Required	Description	Default
`limit`	No	Number of newest records to retrieve (prevents context explosion), retrieves all if not provided.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 11, 2026

TDQS

A3.7/5.0

Behavior1/5

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

The description states the tool 'automatically consumes and clears the atomic memory queue,' which is a destructive side effect. This directly contradicts the annotations declaring readOnlyHint=true and destructiveHint=false. The description reveals a behavior that the annotations claim does not exist, creating a serious inconsistency for the agent.

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?

The description is two sentences: it front-loads the step context, states the primary action, and then discloses the automatic queue clearing behavior. Every sentence adds value with no redundancy or fluff.

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

Completeness5/5

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

Given the tool's simplicity (one parameter, no output schema), the description provides sufficient context: what data is retrieved, where it comes from, and the queue-clearing side effect with its rationale (prevent overflow). It is complete for an agent to understand the tool's role and behavior.

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?

The schema description covers 100% of the single parameter 'limit' with a clear explanation ('Number of newest records to retrieve, prevents context explosion, retrieves all if not provided'). The description does not add any extra parameter guidance, so the baseline 3 applies.

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 clearly states the tool's action: 'Retrieves the merged high-fidelity JSON log datasets processed by the data pipeline.' It also labels it as 'Step 2: Data Observation,' which distinguishes it from sibling tools like init_ruishu_hook and execute_page_action by positioning it as the data retrieval step in a workflow.

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 phrase 'Step 2: Data Observation' provides clear sequential context, implying this tool is used after initialization and before/after executing actions. However, it does not explicitly state when not to use it or name alternative tools, so it falls short of a perfect 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server