Skip to main content
Glama
Sign In
mihomo_party

mihomo_party

by bfrontend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

switch_profile

Switches the active Clash/mihomo subscription or profile by name, letting you change which proxy configuration is currently in use.

Instructions

切换当前活动订阅/profile（按名称）。

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": {
      "profile": "<profile>"
    },
    "name": "switch_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.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 carries the full burden for a state-mutating operation. It does not say whether the switch persists across sessions, whether reload_config must be called afterward, what happens on an unknown profile name, or whether errors are returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with zero filler, and the key qualifier about the argument is placed immediately after the action. Its brevity is close to terseness rather than padding, so it is efficient but under-informative.

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

Completeness2/5

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

For a parameterized state-changing tool with no annotations and no output schema, the definition omits side effects, failure modes, and post-switch steps. An agent could invoke it, but only by guessing at the surrounding workflow.

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

Parameters2/5

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

Schema description coverage is 0%, so the single 'profile' parameter is undocumented in structured data. The phrase '(按名称)' adds only that a name (not an ID) is expected; format, case sensitivity, and enumeration of valid values are all left unspecified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb plus resource ('切换当前活动订阅/profile'), making clear this changes which profile is active rather than merely reading it. It implicitly distinguishes itself from siblings like get_active_config and list_profiles, though it never names them.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of the obvious companion call list_profiles to discover valid names. The parenthetical '(按名称)' only hints at how the argument is supplied, leaving the agent to infer the workflow.

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