Skip to main content
Glama

查看采集状态

see_status

Check whether screen capture is running and inspect ffmpeg path, source, quality, pacing, region, frame/image counts, errors, and stderr tail to diagnose missing or blank output.

Instructions

返回当前采集是否在跑、ffmpeg 路径与来源、采集源/画质/节奏/区域、已见帧数/出图数、错误与 ffmpeg stderr 尾部。排查「看不到画面」时先调它。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description bears the full disclosure burden. It does well on observable output (running state, counters, error strings, ffmpeg stderr tail) and implies a read-only, no-side-effect call, but never states that it is side-effect free, whether it may block while ffmpeg starts, or whether the stderr tail is truncated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences: the field enumeration first, the diagnostic routing second, so the key information is front-loaded. The field list is dense but each item maps to a concrete diagnostic signal, so it earns its space; minor compression is possible.

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

Completeness5/5

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

No output schema exists, so the description must carry the return-value burden itself – and it enumerates every important field (running state, ffmpeg path/source, capture settings, counters, errors, stderr tail). For a no-argument read tool this leaves nothing an agent needs missing.

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 schema has zero parameters, so there is nothing for the description to disambiguate. The baseline for a no-parameter tool applies, and the description correctly does not invent or imply any inputs.

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 opens with a concrete verb and resource ("返回当前采集是否在跑" – returns whether capture is currently running) and then enumerates exactly what the payload contains: ffmpeg path and source, capture source/quality/rhythm/region, frame and image counters, errors, and stderr tail. That content list makes it easy to separate from see_screen/see_region/see_stop, though no sibling is named explicitly.

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 triggering condition plus ordering: when troubleshooting "看不到画面" (can't see the picture), call this first. That is a clear when-to-use statement. It stops short of saying when not to use it or naming which sibling to call next, so it is strong but not exhaustive.

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