Skip to main content
Glama

停止采集

see_stop

Stops the persistent screen capture and frame-scoring process to reduce CPU use when the screen is no longer being monitored. Capture restarts automatically the next time screen viewing is requested.

Instructions

停掉常驻的屏幕采集和判帧。用户不再看屏幕、或你要避免后台吃 CPU 时调用。下次 see_screen 会自动重启。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations, the description carries the full burden and does well: it discloses that this halts a resident background process, that the motivation is CPU cost, and that the effect is reversible because the next see_screen call restarts capture. It omits what happens if capture is not currently running (no-op vs. error) and what the call returns.

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?

Three short sentences, front-loaded with the action, then the trigger, then the restart consequence. No filler or repetition.

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 zero-parameter lifecycle toggle this covers effect, motivation, and reversibility. The only gap is the absence of any statement about the result of the call (success/no-op/error), which matters slightly more here since no output schema exists.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies.

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 (停掉/stop) applied to a specific resource (常驻的屏幕采集和判帧 – the resident screen capture and frame-judging loop), and names the sibling see_screen as the thing that restarts it, so the agent can place it in the lifecycle without opening any 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 two concrete trigger conditions: the user is no longer watching the screen, or you want to avoid background CPU consumption. It does not spell out a when-not case or contrast with see_region/see_status, but the usage context is clear enough to act on.

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