Skip to main content
Glama
Jaggerxtrm

Qwen MCP Tool

by Jaggerxtrm
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Help

Display help information for the Qwen CLI tool to understand available commands and usage instructions.

Instructions

Display Qwen CLI help information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/simple-tools.ts:36-49 (handler)
    The 'helpTool' UnifiedTool defining the 'Help' tool. Includes the execute handler logic that runs the Qwen CLI with --help flag using executeSimpleCommand.
    export const helpTool: UnifiedTool = {
  name: "Help",
  description: "Display Qwen CLI help information",
  category: "simple",
  zodSchema: z.object({}),
  execute: async () => {
    return executeSimpleCommand(CLI.COMMANDS.QWEN, ["--help"]);
  },
  prompt: {
    name: "help",
    description: "Show Qwen CLI help and available options",
    arguments: []
  }
};
  • src/tools/simple-tools.ts:40-40 (schema)
    Zod input schema for the Help tool (no parameters required).
    zodSchema: z.object({}),
  • src/tools/index.ts:11-11 (registration)
    Registration of the helpTool in the tools registry.
    registerTool(helpTool);

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Display' suggests a read-only operation that shows information, but it doesn't specify whether this triggers any side effects (like logging usage), whether authentication is needed, if there are rate limits, or what happens if the CLI isn't properly configured. The description is minimal and lacks important behavioral context for a tool that interacts with system components.

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 perfectly concise at just four words: 'Display Qwen CLI help information.' Every word earns its place - 'Display' specifies the action, 'Qwen CLI' identifies the system, and 'help information' defines the resource. There's zero redundancy or unnecessary elaboration for such a straightforward tool.

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?

Given the tool's simplicity (no parameters, no output schema, no annotations), the description is adequate but has clear gaps. It explains what the tool does at a basic level but doesn't provide enough context about what 'help information' includes, how it's presented, or what users should expect. For a help tool that might be crucial for onboarding or troubleshooting, more detail about the nature and format of the help would be beneficial.

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 has zero parameters, and schema description coverage is 100% (since there are no parameters to describe). The description appropriately doesn't waste space discussing nonexistent parameters. A baseline of 4 is appropriate for zero-parameter tools where the schema fully covers the parameter situation.

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 clearly states the tool's purpose with a specific verb ('Display') and resource ('Qwen CLI help information'). It distinguishes itself from siblings like 'ask-qwen' (which likely queries the AI) and 'ping' (which likely checks connectivity) by focusing on help documentation display. However, it doesn't explicitly mention what format the help information appears in or whether it's general vs. specific help.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention whether this should be used for general CLI overview, command-specific help, troubleshooting, or as a first step for new users. With siblings like 'ask-qwen' that might provide interactive assistance, there's no differentiation about when help display is preferable to asking the AI directly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jaggerxtrm/qwen-mcp-tool'

If you have feedback or need assistance with the MCP directory API, please join our Discord server