Skip to main content
Glama

Add a text node

playground_canvas_add_text
Idempotent

Add an editable text node to a Playground workflow. Supply the latest canvas revision; stale edits are rejected. Returns the text node ID, updated revision and replay status.

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": {
      "projectId": "<projectId>",
      "text": "<text>",
      "expectedRevision": "<expectedRevision>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "playground_canvas_add_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesEditable text to save in the selected text node or workflow input.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
idempotencyKeyYesUnique key for this request; reuse only when retrying the identical request after a lost response. Use a new key after quoting or changing inputs.
expectedRevisionYesCurrent canvas revision from canvas_read; on revision_conflict, read again and rebuild the change.

Output Schema

NameRequiredDescriptionDefault
nodeIdYes
replayedYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=true and destructive=false, so safety and replay semantics are covered. The description adds genuine context beyond them by disclosing the optimistic-concurrency rule (stale edits rejected) and the returned fields (node ID, updated revision, replay status), but since an output schema exists, the return-value sentence adds little.

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 compact sentences with the action stated first, then the constraint, then the return shape. Every sentence carries information; nothing is padded.

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 4-required-param mutation with full schema coverage, annotations and an output schema, the description covers the action, the concurrency prerequisite and the response. It is nearly complete, with only the add-vs-update routing left to inference.

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% and all four parameters are documented, so the schema carries the load. The phrase "supply the latest canvas revision; stale edits are rejected" reinforces expectedRevision's purpose but largely restates the schema's own note about reading again on revision_conflict.

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: "Add an editable text node to a Playground workflow." The add-vs-update distinction from playground_canvas_update_text is implied by the verb, but no sibling is named explicitly, keeping it just short of a 5.

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?

Implies usage by requiring "the latest canvas revision" and warning that "stale edits are rejected," which tells an agent when a call will fail. However, it never says when to add a new node versus updating an existing one via playground_canvas_update_text, so the alternative-selection guidance is missing.

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.