Skip to main content
Glama
Sign In
qwen-cli-mcp

qwen-cli-mcp

by minmax
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

qwen_sessions

List all qwen sessions with working directories, newest first, including running, finished, or timed-out, to recover an ID for qwen_reply.

Instructions

List all qwen sessions started through this server, newest first, with their working directory — running or finished, including runs that timed out. Use it to recover an id for qwen_reply. For turns still executing (qwen_send targets), use qwen_running.

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": "qwen_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.7/5.0
Behavior4/5

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

No annotations provided, so the description carries the full burden. It discloses that it lists both running and finished runs including timeouts, and orders them newest first. This is a read-only listing operation with no hidden side effects; the description adequately conveys its behavior without needing to mention permissions or rate limits.

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?

Two sentences, front-loaded with the core listing purpose and ordering, followed by usage guidance. No filler words; every sentence earns its place.

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

Completeness5/5

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

For a zero-parameter, no-output-schema tool, the description covers everything an agent needs: what it lists, the ordering, scoping to this server, inclusion of timeouts, and how to use it for id recovery. It also points to the sibling for a different case. Nothing is missing.

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, so the baseline is 4. The description doesn't need to explain parameter meanings since there are none, and it doesn't attempt to add any.

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

Purpose5/5

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

The description states a specific verb (List) and resource (qwen sessions), with details: newest first, with working directory, running or finished, including timeouts. It distinguishes from siblings by referencing qwen_reply and qwen_running, making the purpose unmistakable.

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

Usage Guidelines5/5

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

Explicitly instructs to use it to recover an id for qwen_reply, and tells when NOT to use it: 'For turns still executing (qwen_send targets), use qwen_running.' This gives clear when-to-use and alternatives.

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