Skip to main content
Glama

Get canvas

snipaya_get_canvas
Read-only

Retrieve open tabs and active canvas details—images, annotations, selection, and crop—to inspect current state before annotating or editing screenshots.

Instructions

Describe the open tabs and the active canvas: images (id, position, size, original pixel size), annotations (id, kind, geometry, style, text, anchors), selection and crop. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
tabIdNoTarget tab id. Defaults to the active tab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that by disclosing the shape of what comes back (id, position, size, original pixel size, geometry, style, text, anchors) and by stating the sequencing convention, which is not derivable from annotations or schema.

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?

Two short sentences, no filler: the first enumerates the returned state, the second delivers the ordering rule. The most actionable instruction ('Call this first') is placed at the end as a clean imperative rather than buried in prose.

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 read-only introspection tool with one optional param and no output schema, the description carries the return-value burden and does enumerate the major payload sections. Slightly more detail on nesting (e.g., how annotations relate to images) would make it fully self-sufficient.

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?

Only one optional parameter with 100% schema description coverage, so the schema already explains tabId and its active-tab default. The description reinforces tab scoping by referring to 'the active canvas' but adds no syntax, format, or fallback detail beyond the schema — 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?

Names a concrete verb+resource ('Describe the open tabs and the active canvas') and enumerates exactly what state is reported (images, annotations, selection, crop), which distinguishes it from the add_*/update_items mutation siblings. The verb 'Describe' is slightly soft — an agent could momentarily read it as generating prose rather than returning structured state — but the field list resolves that.

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?

'Call this first' gives explicit ordering guidance that tells the agent to anchor on this read before issuing edits. It does not name alternatives or exclusions (e.g., versus snipaya_tabs or snipaya_select), so it stops short of full when/when-not routing.

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