Skip to main content
Glama

看屏幕工具的完整手册

see_help

Returns detailed guidance on choosing screen-capture parameters, covering quality/token tradeoffs, pace thresholds, region usage, platform dependencies, and limitations. Call when unsure how to configure settings.

Instructions

返回画质/token 换算、三档节奏的门槛、区域与逐场景用法、平台依赖、已知限制等详细说明。不确定参数怎么选时调它。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden, and it does disclose the substance of the response by enumerating the topics covered. It stops short of stating that the call is side-effect free and read-only, or whether the content is static reference text versus platform-dependent state, which would matter for caching decisions.

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 compact sentences: the first front-loads the coverage list, the second delivers the usage trigger. Nothing is redundant, and the operative instruction comes last where it is easy to act on.

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?

With no output schema and no parameters, the description must convey what comes back, and the topic enumeration does that well enough to justify the call. The only soft spot is not characterizing the return format (plain text vs structured reference), which is minor for a help tool.

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?

Zero-parameter tool, so the baseline is 4. The description uses its single clause to position the tool relative to parameter selection elsewhere, which is the only meaningful semantic available without a schema.

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 concrete deliverable (a manual covering quality/token conversion, pace-tier thresholds, region and per-scene usage, platform dependencies, known limitations), so an agent knows this is the documentation tool rather than a capture action. It does not explicitly contrast itself with see_screen/see_region/see_stop, but the 'help' framing is inherently distinct from those action siblings.

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 an explicit trigger condition: call it when unsure how to choose parameters. That is clear positive guidance, though it offers no when-not condition (e.g., skip it if you already know the tier/quality you want) and no mention of whether the returned reference should be cached between calls.

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