Skip to main content
Glama

设置只看屏幕的某一块

see_region

Restrict screen capture to one physical-pixel rectangle (x,y,w,h), such as a phone window or video player, and pass "off" to cancel.

Instructions

限定之后所有看屏幕只采这一块(例如手机竖屏窗口、播放器画面、某个聊天窗口)。坐标是屏幕物理像素,格式 "x,y,w,h",例如 "100,200,800,600"。传 "off" 取消。设置后当前采集会重启(约 0.6 秒)。区域持久化在 ~/.mcp-see-screen/region.json。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "region": "<region>"
    },
    "name": "see_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionYes"x,y,w,h" 物理像素整数,或 "off" 取消

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does well: it discloses that the setting restarts the current capture (~0.6 seconds of disruption), that the value persists across sessions at ~/.mcp-see-screen/region.json, and that coordinates are physical screen pixels. What it omits is failure behavior — invalid formats or regions outside screen bounds are not described.

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?

Four short sentences, front-loaded with the effect, then format, then cancellation, then side effects. Nothing is redundant and every clause carries operational information.

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 tool with no output schema and no annotations, it covers effect scope, unit format, cancellation, latency cost, and persistence location — everything an agent needs to invoke it safely. The only gap is unspecified error/validation behavior for malformed or out-of-bounds regions.

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 schema already defines the single 'region' string and the 'off' sentinel. The description adds value by specifying physical-pixel units and giving a concrete worked example ('100,200,800,600'), which clarifies ordering and units beyond the schema's terse text.

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?

States a specific verb and object: restrict all subsequent screen captures to one rectangle, with examples (portrait phone window, player frame, chat window) that make the effect concrete. The phrase '之后所有看屏幕' explicitly ties this setting to the capture tool, distinguishing it from see_screen/see_status/see_stop without needing the sibling schema.

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?

Gives clear usage context through three scenarios where cropping is appropriate, and states the inverse operation ('传 "off" 取消'). It does not say when not to use it or what happens if a sibling like see_stop is called first, but the trigger condition for this tool is unambiguous.

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