Ruishu MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| init_ruishu_hookA | Step 1: Pipeline Initialization. Binds the system-level probe to the target environment to extract high-quality business data from complex dynamic environments. Decouples caching and ServiceWorker proxy layers for pure telemetry. |
| get_intercepted_trafficA | 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. |
| execute_page_actionA | Auxiliary action: allows executing specified JS in the page (simulate click/scroll/input, etc.) to trigger requests. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct role in the pipeline: initialization, data retrieval, and page interaction. There is no overlap in purpose or ambiguity about which tool to use.
All tool names follow a consistent verb_noun pattern: init_riushu_hook, get_intercepted_traffic, execute_page_action. This makes the set predictable and easy to navigate.
With only three tools, the server is tightly scoped to a specific workflow. Each tool is necessary and contributes to a coherent pipeline without unnecessary bloat or missing essentials.
The tool set covers the full lifecycle of the interception workflow: setup, observation, and action. There are no obvious dead ends or missing operations required to accomplish the intended purpose.