Skip to main content
Glama
Sign In
@qirabot/mcp

@qirabot/mcp

by qirabot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

take_screenshot

Capture a live screenshot of a device screen to inspect UI or verify results after automation tasks.

Instructions

Capture a live screenshot of the device's current screen. Returns the image directly (synchronous, up to 30s).

Use this tool when:

  • You need to see what is currently displayed on the device screen.

  • You want to verify the result after a run_task completes.

  • You need to inspect the UI before deciding what action to take.

This returns the real-time screen.

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": {
      "device_id": "<device_id>"
    },
    "name": "take_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_idYesThe device ID to capture a screenshot from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses synchronous behavior, 30s timeout, and that it returns the image directly. Could mention permissions but overall good.

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 concise sentences with front-loaded purpose, usage guidelines, and behavior. No redundant information.

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?

Given the tool's simplicity (one param, no output schema), description covers purpose, usage, behavior (sync, timeout, return type), and context. No gaps.

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 already describes the single parameter (device_id) with 100% coverage. Description adds no extra meaning beyond the schema, so baseline score of 3 is appropriate.

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?

Description clearly states 'Capture a live screenshot of the device's current screen', with a specific verb and resource. It distinguishes itself from sibling tools (none of which are screenshot-related).

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?

Description explicitly lists three use cases: seeing the screen, verifying task results, and inspecting UI. It lacks explicit when-not-to-use but sibling tools don't compete, so it's adequate.

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