Skip to main content
Glama
Sign In
whistle-mcp

whistle-mcp

by 7gugu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

removeValueFromGroup

Remove a specified value from a group within the Whistle MCP Server to streamline proxy management and maintain organized rule configurations.

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

Input Schema

NameRequiredDescriptionDefault
valueNameYes值名称

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/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 the full burden of behavioral disclosure. It only states the action ('remove value from group') without explaining effects (e.g., whether this is destructive, if it requires permissions, or what happens to the value afterward). For a mutation tool with zero annotation coverage, this is a critical gap.

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

Conciseness2/5

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

The description is a single phrase that is overly concise to the point of under-specification. It lacks structure and fails to convey essential details, making it inefficient rather than appropriately brief. Every word should add value, but here it merely repeats the tool name.

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

Completeness1/5

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

Given the complexity of a mutation tool with no annotations and no output schema, the description is severely incomplete. It doesn't explain what the tool returns, error conditions, or behavioral traits. For a tool that modifies data, this leaves the agent with insufficient context to use it correctly.

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 description coverage is 100%, with the single parameter 'valueName' documented as '值名称' (value name). The description adds no additional meaning beyond this, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the schema already provides adequate parameter information.

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 '将值移出分组' (remove value from group) is a tautology that restates the tool name without adding specificity. It doesn't clarify what type of 'value' or 'group' is involved, nor does it distinguish this tool from sibling tools like 'removeRuleFromGroup' or 'deleteValue'. The purpose is stated but lacks meaningful differentiation.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., the value must exist in a group), exclusions, or related tools like 'addValueToGroup' or 'deleteValue'. The description offers no context for appropriate usage.

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