Skip to main content
Glama

update_canvas

DestructiveIdempotent

Actualiza nombre y/o contenido de un canvas

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": {
      "canvas_id": "<canvas_id>"
    },
    "name": "update_canvas"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
contentNoContenido del canvas: el objeto JSON de la escena (nodos y edges)
canvas_idYesID del canvas
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety metadata is covered. The description adds only the partial-update nuance ('y/o'), and crucially omits that supplying 'content' replaces the entire scene object — the destructive behavior the annotation flags. It also says nothing about required permissions or what the response contains.

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?

A single front-loaded sentence with no wasted words. It is efficient, though its brevity borders on under-specification for a destructive mutation with four parameters.

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

Completeness2/5

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

For a destructive, nested-object mutation with no output schema and four parameters, the description should at minimum warn that content overwrites the existing scene and clarify the optional workspace_id resolution. Neither is present, leaving the agent reliant on the schema and annotations alone.

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 75%, so the schema already documents canvas_id, workspace_id, and content (scene JSON). The description merely restates the name/content field names without adding format, constraints, or replacement semantics beyond what the schema provides, matching the baseline for high 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 ('Actualiza') and resource ('canvas') plus the fields affected ('nombre y/o contenido'), so an agent can tell it edits an existing canvas rather than creating or deleting one. It does not explicitly contrast with siblings like create_canvas or get_canvas, but the operation itself is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus create_canvas, get_canvas, or delete_canvas, and no prerequisites or preconditions are stated. The agent must infer from the name alone that this is the edit path for an existing canvas.

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.

Resources