Skip to main content
Glama
Sign In
surge-mcp-server

surge-mcp-server

by DLYZZT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

surge_get_feature_status

Check whether a specific Surge proxy feature (MITM, Capture, Rewrite, or Scripting) is enabled or disabled.

Instructions

Get the status of a Surge feature (MITM, Capture, Rewrite, or Scripting)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "feature": "<feature>"
    },
    "name": "surge_get_feature_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
featureYesThe feature to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must fully convey behavior. It indicates a read operation ('Get') but does not disclose what the returned status looks like, whether there are side effects, or any required permissions.

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 a single sentence with no unnecessary words or information; it is front-loaded with the action and resource.

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

Completeness3/5

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

For a simple getter with one parameter and no output schema, the description is minimal but adequate. However, it does not explain what 'status' means or the format of the result, which could be improved.

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?

Schema coverage is 100% and the description adds value by enumerating the allowed enum values (mitm, capture, rewrite, scripting) beyond the schema's 'The feature to check', making the parameter clearer.

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?

Description uses specific verb 'Get' and resource 'status of a Surge feature', explicitly listing the four possible features (MITM, Capture, Rewrite, Scripting), which clearly distinguishes it from sibling tools like surge_toggle_feature that modify state.

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 description implies reading a feature's status but does not provide explicit guidance on when to use this tool vs alternatives like surge_toggle_feature, nor does it mention any prerequisites or context.

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