Enhance

Review canvas pixels

canvas_render

Render the version returned by a successful read or write and inspect its native PNG. Target the affected screen/node; a blank canvas does not need a pre-render. For a selection link use one node inside the selection. Review after a meaningful visual change, and repeat only after further changes or a real discrepancy.

Input Schema

Name	Required	Description
`scale`	No
`canvas`	Yes
`target`	No
`clientToken`	No	Reuse only when retrying this exact mutation.
`sourceState`	No
`expectedVersion`	Yes	Version returned by the latest successful read or write.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 12, 2026

addedInput schema / properties / scale / exclusiveMinimum
```
Added value: +0
```
removedInput schema / properties / scale / maximum
```
Removed value: -4
```
removedInput schema / properties / scale / minimum
```
Removed value: -0.1
```

changedInput schema / properties / target / oneOf

Previous value: -[
-  {
-    "properties": {
-      "kind": {
-        "const": "content",
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "kind": {
-        "const": "page",
-        "type": "string"
-      },
-      "pageId": {
-        "maxLength": 200,
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "pageId"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "kind": {
-        "const": "node",
-        "type": "string"
-      },
-      "nodeId": {
-        "maxLength": 200,
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "nodeId"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "bounds": {
-        "properties": {
-          "height": {
-            "exclusiveMinimum": 0,
-            "maximum": 100000,
-            "type": "number"
-          },
-          "width": {
-            "exclusiveMinimum": 0,
-            "maximum": 100000,
-            "type": "number"
-          },
-          "x": {
-            "type": "number"
-          },
-          "y": {
-            "type": "number"
-          }
-        },
-        "required": [
-          "x",
-          "y",
-          "width",
-          "height"
-        ],
-        "type": "object"
-      },
-      "kind": {
-        "const": "bounds",
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "bounds"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "kind": {
+        "const": "content",
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "kind": {
+        "const": "page",
+        "type": "string"
+      },
+      "pageId": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "pageId"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "kind": {
+        "const": "node",
+        "type": "string"
+      },
+      "nodeId": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "nodeId"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "bounds": {
+        "properties": {
+          "height": {
+            "exclusiveMinimum": 0,
+            "type": "number"
+          },
+          "width": {
+            "exclusiveMinimum": 0,
+            "type": "number"
+          },
+          "x": {
+            "type": "number"
+          },
+          "y": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "x",
+          "y",
+          "width",
+          "height"
+        ],
+        "type": "object"
+      },
+      "kind": {
+        "const": "bounds",
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "bounds"
+    ],
+    "type": "object"
+  }
+]

First observedOct 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false with a non-destructive profile, and the description adds useful context about needing a read/write version to render and when to re-render. However, it doesn't explain what the render returns, latency, or side effects beyond the annotation hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with no wasted words, front-loading the core action and following with constraints. Some minor redundancy in repeating 'read or write' but generally efficient.

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?

Output schema exists, so return values needn't be explained. For a 6-param tool with 33% coverage and rich nested schema, the description covers the key concepts (versioning, targeting, repeat policy) but leaves some parameter-specific nuance for the agent to infer.

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 description coverage is 33%, so the schema already carries much of the meaning (e.g., expectedVersion description). The description's mention of 'target' and versioning adds minimal detail beyond the schema's target oneOf and expectedVersion field but doesn't fully compensate for the low coverage.

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?

The description names a specific verb (render) and resource (canvas pixels/PNG) and frames it as reviewing a version returned by a read or write. It doesn't explicitly contrast with siblings like canvas_edit or canvas_write_html, so an agent won't know from this alone that this is the only read-back/verification tool.

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?

Provides good when-to-use guidance (after a meaningful visual change) and notes when not to render (blank canvas). It hints at repetition discipline but doesn't name alternatives or explain how it relates to canvas_edit/canvas_write_html.

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

All Enhance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?