Skip to main content
Glama

get_image

Displays a selected frame with all visible layers blended and nearest-neighbour scaling, keeping pixels sharp for inspection.

Instructions

Show a frame with all visible layers blended, scaled up with nearest-neighbour so pixels stay sharp.

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": "get_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameNoFrame index, from 0. Defaults to the current frame
scaleNoZoom factor. Defaults to about 512 px on the long side

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It usefully discloses that all visible layers are composited and that nearest-neighbour scaling keeps pixels sharp, but never explicitly states that the call is non-mutating or what form the returned image takes.

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?

A single well-formed sentence with the compositing behaviour leading and the scaling rationale trailing; nothing is wasted or buried.

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 zero-required-parameter, no-output-schema tool, the description covers what is rendered and how it is scaled, which is enough to call it correctly. The only minor gap is the absence of an explicit statement about the return format (image content vs. metadata).

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%, with both frame and scale already documented in the schema. The description only alludes to scaling ('scaled up with nearest-neighbour') and adds no syntax, bounds, or default behaviour beyond what the schema states, so baseline 3 applies.

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 specific verb (show) and resource (a frame with all visible layers blended), and the nearest-neighbour scaling detail distinguishes it from a raw-pixel reader like read_pixels. It does not explicitly name or contrast a sibling, so it stops short of the top score.

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 only implied: 'show ... layers blended' suggests visual inspection of the composited result rather than raw data or a file export. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. export_png / read_pixels).

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