Skip to main content
Glama
amenalahassa

bugcap

by amenalahassa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Ask the user for a screenshot

request_screenshot

Ask a human to take a screenshot and attach it to a bug report when you need visual evidence you cannot capture yourself; waits until done or timeout.

Instructions

Ask the human at the machine to take a screenshot (for example to show a bug, or to check a fix) and attach it to a report. Use this when you need visual evidence you cannot produce yourself; to attach an image file that already exists, use attach_image. Opens the user's capture tool and blocks until they finish, cancel or timeout_seconds passes. Adds the image to the report (and creates a report for issue if needed). Returns {"status": "captured", "report_id"} plus the screenshot as image content, or a status of "cancelled", "error" or "non_interactive" (no desktop available, e.g. over SSH or in a container) with a message.

Input Schema

NameRequiredDescriptionDefault
noteNoText appended to the report's notes and tied to the new screenshot, e.g. 'after the fix'.
issueNoGitHub issue to attach it to instead, as 'owner/repo#123' or '123' for the repo configured in .bugcap.toml. A report is created for the issue if none exists yet.
messageNoWhat you want the user to capture, shown to them before the capture tool opens.
report_idNoReport to attach the screenshot to. Give this or `issue`; this wins if both are set.
timeout_secondsNoHow long to wait for the user before giving up, in seconds (default 300).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.7.2
    • addedInput schema / properties / issue / description
      Added value: +"GitHub issue to attach it to instead, as 'owner/repo#123' or '123' for the repo configured in .bugcap.toml. A report is created for the issue if none exists yet."
    • addedInput schema / properties / message / description
      Added value: +"What you want the user to capture, shown to them before the capture tool opens."
    • addedInput schema / properties / note / description
      Added value: +"Text appended to the report's notes and tied to the new screenshot, e.g. 'after the fix'."
    • addedInput schema / properties / report_id / description
      Added value: +"Report to attach the screenshot to. Give this or `issue`; this wins if both are set."
    • addedInput schema / properties / timeout_seconds / description
      Added value: +"How long to wait for the user before giving up, in seconds (default 300)."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare safe non-destructive mutation; the description adds substantial behavior: it opens the user's capture tool, blocks until completion/cancel/timeout, may create a report for an issue, and lists exact return statuses including 'non_interactive' for SSH/container environments. That goes well beyond annotation coverage.

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?

Front-loaded with the core action, then usage, blocking behavior, side effects, and return values. Each sentence contributes distinct information and there is no repetition.

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?

Covers all the hard parts: blocking semantics, side effects, alternative tool, environmental failure mode, and return shape. With no output schema, the description fully explains outcomes.

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 all parameters are already documented in detail. The description adds only high-level references to timeout and report creation, which the schema already states; baseline 3 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 and resource ('ask the human... to take a screenshot') and explicitly distinguishes it from the sibling attach_image. Examples of when the resource is useful reinforce the purpose without ambiguity.

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

Usage Guidelines5/5

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

Explicitly says when to use it ('when you need visual evidence you cannot produce yourself') and names the alternative ('to attach an image file that already exists, use attach_image'). No inference required.

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