Skip to main content
Glama
Sign In
whistle-mcp

whistle-mcp

by 7gugu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

createGroup

Creates a new group for organizing and managing Whistle proxy rules and configurations using the Whistle MCP Server. Simplifies proxy management by enabling structured rule grouping.

Instructions

创建新分组

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

Input Schema

NameRequiredDescriptionDefault
nameYes分组名称

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. '创建新分组' only indicates it's a creation operation without specifying what happens after creation, whether it requires specific permissions, if it's idempotent, what error conditions exist, or what the response contains. For a mutation tool with zero annotation coverage, this is severely inadequate.

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?

The description is extremely concise - just three Chinese characters. While this could be considered under-specified rather than appropriately concise, it's front-loaded and contains no wasted words. The single phrase directly states the core function without unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what a 'group' represents in this context, what happens after creation, or what the tool returns. Given the complexity implied by many sibling tools for managing groups, rules, and values, more context is needed for the agent to use this effectively.

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 input schema has 100% description coverage with the 'name' parameter clearly documented in Chinese. The description doesn't add any parameter information beyond what's in the schema. With complete schema coverage, the baseline score of 3 is appropriate since the schema does the heavy lifting for parameter documentation.

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

Purpose2/5

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

The description '创建新分组' (Create new group) restates the tool name 'createGroup' with minimal elaboration. It specifies the verb 'create' and resource 'group', but doesn't distinguish it from sibling tools like 'createRule', 'createValue', or 'createValuesGroup'. The description is tautological rather than explanatory.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when not to use it, or how it relates to sibling tools like 'renameGroup', 'deleteGroup', or other group-related operations. There's complete absence of contextual usage information.

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

Related Tools