Skip to main content
Glama

qq_screenshot

Read-only

Captures the QQ client's virtual display—QQ window by default or full screen—so you can inspect login prompts, security checks, and update notices.

Instructions

Screenshot of the virtual display the QQ client runs on (the QQ window by default, or the full screen). Use it to see dialogs such as login prompts, security checks or update notices.

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_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
full_screenNoCapture the whole display instead of just the QQ window

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: the capture targets a virtual display the client runs on, defaults to the QQ window, and is meant for transient dialogs that may otherwise be invisible to other tools. It does not say what is returned (inline image versus file path), which is the main remaining behavioral gap.

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 front-loads what is captured and the default scope, the second gives the trigger scenario. No filler, no repetition of the schema, nothing an agent must skim past.

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 single-parameter, read-only tool with full schema coverage and annotations, the description covers purpose, scope, and typical use cases adequately. The one omission is the return format, which no output schema supplies, so an agent cannot predict whether it receives an image or a path.

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?

Schema description coverage is 100%, so the single full_screen parameter is already documented in the schema. The description restates the default-versus-full-screen distinction, adding slight reinforcing context but no new syntax or semantics beyond the schema, so the baseline 3 applies.

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 the exact resource captured ('the virtual display the QQ client runs on') and the default scope ('the QQ window by default, or the full screen'), which is concrete and distinguishable from siblings like qq_click or qq_login_status. It stops short of explicitly contrasting itself with any named sibling, which keeps it from a 5.

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

Usage Guidelines4/5

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

It gives a clear use case: 'Use it to see dialogs such as login prompts, security checks or update notices.' That tells an agent when this tool is the right one. There are no stated exclusions or alternatives for when not to screenshot, so it falls short of the top band.

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