Skip to main content
Glama
Sign In
mihomo_party

mihomo_party

by bfrontend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_profiles

List current proxy groups and their selectable nodes from the running configuration so you can inspect available routing options before switching.

Instructions

列出当前代理组及每个组可选节点（运行配置）。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/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; it does convey that the read reflects the current running state and that each group's selectable nodes are included. However, it does not state read-only safety, pagination, or whether inactive/disabled nodes are filtered out.

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?

A single front-loaded sentence with no redundant padding. The trailing parenthetical '（运行配置）' is terse to the point of ambiguity about whether it describes the scope of the listing or the source of the data.

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?

With no annotations and no output schema, the description should say more about the shape of the result — whether a flat list of groups, group names with node arrays, or which node is currently selected. It also leaves the 'profiles' vs 'proxy groups' terminology unresolved for a tool sitting alongside switch_profile.

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?

The tool takes zero parameters, so there is nothing beyond the schema to explain; the baseline of 4 applies. The description correctly adds no parameter noise.

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

Purpose3/5

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

The description gives a specific verb and resource ('列出当前代理组及每个组可选节点'), but the tool name 'list_profiles' refers to profiles while the text describes proxy groups and nodes, creating a naming mismatch that could confuse an agent comparing it with switch_profile. It does not explicitly distinguish itself from get_active_config, which also concerns the running configuration.

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 statement of when to use this tool versus get_active_config, switch_profile, or select_proxy. The parenthetical '（运行配置）' implies it reads live state, but this is inference rather than guidance, and no exclusions or prerequisites are given.

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