Skip to main content
Glama

qq_type

Types text or sends key presses (e.g., Return, Tab, Ctrl+A) to the focused QQ window, enabling verification code entry and keyboard shortcuts.

Instructions

Type text or press keys in the focused QQ window (e.g. a verification code). keys uses xdotool names: "Return", "Tab", "ctrl+a", "BackSpace", "Escape".

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

Input Schema

NameRequiredDescriptionDefault
keysNoKeys to press after the text
textNoText to type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the description's job is to add operationally useful detail — which it does by disclosing the xdotool key-name convention with concrete examples and the requirement that the target window be focused. It stops short of describing what happens on failure (e.g. no focused window, unknown key name).

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 tight sentences: the first states the action and scope, the second supplies the key-format detail. Nothing is redundant and the core capability is front-loaded.

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

Completeness4/5

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

For a two-parameter input tool with no output schema, the description covers the essentials: what it does, the focus precondition, and the key syntax. It leaves minor gaps around combination semantics for text+keys and error behavior, but nothing that would prevent a correct call.

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?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning beyond the terse schema text by specifying that keys use xdotool names and giving examples like "ctrl+a" and "Return". It does not clarify whether text and keys can be supplied together or in what order, which the schema only partially implies.

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 names a specific verb pair ("Type text or press keys") and a specific target ("the focused QQ window"), making the action unambiguous. It implicitly contrasts with click-based siblings like qq_click by emphasizing keyboard input, but never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage context is implied rather than stated: the tool only works on the already-focused QQ window, and the verification-code example illustrates a concrete scenario. There is no explicit when-not guidance or instruction to focus the window first (e.g. via qq_click) before calling.

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