Skip to main content
Glama

proxy_stop_transparent

Stop the transparent proxy listener to disable automatic traffic interception. Use this to halt network capture or restore normal browsing without proxy interference.

Instructions

Stop the transparent proxy listener.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the proxy_stop_transparent tool. It calls proxyManager.stopTransparent() and returns a success/error JSON response.
    async () => {
      try {
        await proxyManager.stopTransparent();
        return {
          content: [{
            type: "text",
            text: JSON.stringify({ status: "success", message: "Transparent proxy stopped." }),
          }],
        };
      } catch (e) {
        return { content: [{ type: "text", text: JSON.stringify({ status: "error", error: String(e) }) }] };
      }
    },
  • The schema for proxy_stop_transparent: no input parameters (empty object {})
    {},
  • Registration of the 'proxy_stop_transparent' tool on the MCP server via server.tool()
    server.tool(
      "proxy_stop_transparent",
      "Stop the transparent proxy listener.",
      {},
      async () => {
        try {
          await proxyManager.stopTransparent();
          return {
            content: [{
              type: "text",
              text: JSON.stringify({ status: "success", message: "Transparent proxy stopped." }),
            }],
          };
        } catch (e) {
          return { content: [{ type: "text", text: JSON.stringify({ status: "error", error: String(e) }) }] };
        }
      },
    );
  • src/index.ts:72-72 (registration)
    Top-level registration: registerTransparentTools(server) is called in the MCP server setup
    registerTransparentTools(server);
  • The underlying ProxyManager.stopTransparent() method that stops the transparent proxy server instance (mockttp) and sets _transparentRunning to false.
    async stopTransparent(): Promise<void> {
      if (!this._transparentRunning) {
        throw new Error("Transparent proxy is not running.");
      }
      if (this.transparentServer) {
        await this.transparentServer.stop();
        this.transparentServer = null;
      }
      this._transparentRunning = false;
    }
Behavior2/5

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

No annotations provided, so description must carry behavioral disclosure. Only states 'stop' with no details about side effects, preconditions, or safety. Insufficient for a mutation tool.

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?

Extremely concise, single sentence with no wasted words. Appropriate for a simple stop action.

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 tool with no parameters and no output schema, the description is mostly adequate, though lacking usage context.

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

Parameters4/5

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

Zero parameters; baseline score of 4 applies. Description does not need to add parameter meaning.

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?

Clearly states the verb 'Stop' and the resource 'transparent proxy listener', differentiating from siblings like proxy_stop and proxy_start_transparent.

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 guidance on when to use this tool versus alternatives such as proxy_stop or proxy_transparent_status. Lacks context for decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yfe404/proxy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server