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

surge-mcp-server

by DLYZZT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

surge_set_outbound_mode

Control traffic routing by setting outbound mode to direct, proxy, or rule.

Instructions

Set the outbound mode (direct, proxy, or rule)

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": {
      "mode": "<mode>"
    },
    "name": "surge_set_outbound_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesThe outbound mode to set

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are present, and the description does not disclose any side effects, such as whether setting the mode disrupts current connections or affects policies. As a mutation tool, this is insufficient.

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, directly stating the purpose and options. It is efficiently front-loaded with no extraneous information.

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 set operation with one well-defined parameter, the description is nearly sufficient. However, the lack of behavioral context and output information leaves some gaps.

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 provides full coverage of the single parameter with an enum. The description merely restates the enum values without adding semantic depth, so no value beyond the schema.

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 action ('Set') and the resource ('outbound mode') with the allowed values (direct, proxy, or rule). It is easily distinguishable from the sibling tool 'surge_get_outbound_mode' which retrieves the mode.

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 is provided on when to use this tool, prerequisites, or when to avoid it. There is no mention of alternative tools or context for choosing one mode over another.

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