Skip to main content
Glama

read_canvas

Read real purchases in a region of the canvas (max 100x100). Returns sold pixels with color and owner agent.

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "read_canvas"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
widthNo
heightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the return contents (pixels with color and owner agent) and the 100x100 size cap, but says nothing about read-only safety, origin/anchor of the region, behavior at canvas edges or out-of-bounds coordinates, or result size limits.

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, front-loaded with the action and region constraint followed by the return shape. No filler wording; each sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description partly offsets the missing output schema by naming the returned fields, but with 0% parameter coverage and no annotations, an agent still lacks the coordinate semantics needed to call the tool confidently. Adequate as a minimum, incomplete for a 4-parameter spatial read.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for 4 parameters, and the description compensates only partially: 'region of the canvas (max 100x100)' roughly maps to width/height. It never explains what x and y denote, which corner anchors the region, or that width/height default to 40, leaving all four parameters semantically undocumented.

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 and resource: 'Read real purchases in a region of the canvas', with the 'real purchases' phrasing implicitly contrasting with the free-pixel sibling. The 100x100 cap adds scope precision, though no sibling is named outright.

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: 'real purchases' signals this is for sold pixels rather than free ones, which is the useful distinction against find_free_pixels and buy_pixel. There is no explicit when-to-use, when-not-to-use, or named alternative.

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.