Skip to main content
Glama

get_screenshot_detail

Retrieve captured text and metadata for a specific context-moment screenshot ID, and check whether encrypted pixels exist without returning decrypted pixels or file paths.

Instructions

Get captured text and metadata for one context-moment id. It reports whether encrypted pixels exist but never returns decrypted pixels or a file path. Requires the separate screen-memory permission.

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": {
      "snapshot_id": "<snapshot_id>"
    },
    "name": "get_screenshot_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
snapshot_idYesScreenshot id returned by search_screen or get_timeline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 encrypted pixels are reported only as existence, that decrypted pixels and file paths are never returned, and that a separate screen-memory permission is required. It omits read-only framing details and error/permission-failure behavior, but the key limits and auth need are stated.

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 core action, then the return limits, then the permission prerequisite. No filler or redundancy.

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 one-parameter detail lookup with no output schema, the description covers what is returned, what is deliberately withheld, and the auth requirement. Minor gaps remain around output shape and behavior when the id is invalid or permission is missing.

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% and the single parameter is already fully documented as a screenshot id from search_screen or get_timeline. The description reinforces that exactly one context-moment id is accepted, but adds no format or constraint detail beyond the schema baseline.

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?

States a concrete verb and resource: 'Get captured text and metadata for one context-moment id', and scopes it to a single id. It does not explicitly contrast itself with list-style siblings like search_screen or get_timeline, so differentiation is only implied via the id parameter.

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

Usage Guidelines3/5

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

Usage is implied — you call it with an id that search_screen or get_timeline returned — and the 'Requires the separate screen-memory permission' line surfaces a real prerequisite. However, there is no explicit when-to-use versus alternatives statement or when-not guidance.

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