Skip to main content
Glama

Take phone screenshot

phone-snapshot-tool
Read-only

Capture a JPEG snapshot of a farm phone screen. Use it to see what is on screen before and after phone-control-tool input. The phone must show video_live: true in list-phones-tool.

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": {
      "slot": "<slot>"
    },
    "name": "phone-snapshot-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotYesPhone slot to snapshot, given as the `slot` UUID from list-phones-tool (its display name like "slot12" is not accepted). The phone must show `video_live: true` there.
widthNoSnapshot width in pixels. Defaults to the configured farm width. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / slot / description
      Previous value: -"Phone slot to snapshot, given as the `slot` UUID from list-phones (its display name like \"slot12\" is not accepted). Must be cast/live."New value: +"Phone slot to snapshot, given as the `slot` UUID from list-phones-tool (its display name like \"slot12\" is not accepted). The phone must show `video_live: true` there."
    • addedInput schema / properties / width / maximum
      Added value: +2000
    • addedInput schema / properties / width / minimum
      Added value: +120
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds the useful precondition of `video_live: true` and discloses the return format as a JPEG, which matters because no output schema exists. It does not cover how the image is delivered (inline vs. URL) or whether the call fails or blocks when a phone is not live, leaving the failure mode implicit.

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 purpose, then workflow, then precondition. No filler or redundant restatement of the tool name.

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 two-parameter read-only capture tool with no output schema, the description supplies purpose, format, workflow placement, and the prerequisite state. The remaining gap is the shape of the response payload (inline image vs. reference), though the format itself is stated.

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 coverage is 100%: the schema already explains that `slot` is the UUID from list-phones-tool rather than the display name, and documents `width` bounds and default. The description only repeats the `video_live` requirement and adds no new syntax or format detail, so the baseline of 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?

Names a specific verb ('Capture'), resource ('a farm phone screen'), and output format ('JPEG snapshot') in the first sentence. An agent can distinguish this from phone-ocr-tool or phone-control-tool 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 an explicit usage context - verify the screen before and after phone-control-tool input - which tells the agent when to reach for it. It also states the precondition that the phone must show `video_live: true`. It stops short of naming when not to use it (e.g., for text extraction), but the named workflow is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources