Skip to main content
Glama

Get one Playground node

playground_node_get
Read-onlyIdempotent

Read one node by ID with its incoming and outgoing connections, its group children, and the current canvas revision. Cheaper than reading the whole graph.

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>",
      "nodeId": "<nodeId>"
    },
    "name": "playground_node_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesExisting canvas node ID returned by canvas_read, node search or creation.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.

Output Schema

NameRequiredDescriptionDefault
nodeYes
childIdsYes
incomingYes
outgoingYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered. The description adds genuine value beyond that by disclosing the content envelope of the read — connections in both directions, group children, and the current canvas revision — which tells the agent it can avoid follow-up calls. It does not mention failure modes such as a stale or nonexistent node ID.

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 sentences, no filler, and the return-scope information is front-loaded ahead of the cost comparison. Every clause earns its place.

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?

With an output schema present and rich annotations, the description need not explain return shapes, and it correctly focuses on scope and cost. It is nearly complete for a two-parameter read, though it leaves unstated what happens when the node ID is stale or the project mismatched — relevant given a read is often a precondition for canvas mutations.

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 100%, and both nodeId and projectId have their own schema descriptions covering provenance (from canvas_read, search, or creation) and UUID format. The description only re-states "by ID" and adds no format, sourcing, or edge-case detail, so the schema does the heavy lifting.

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 gives a specific verb and resource ("Read one node by ID") plus the exact payload scope (connections, group children, canvas revision). It implicitly contrasts with a whole-graph read via "Cheaper than reading the whole graph," but never names the sibling it competes with, so differentiation is contextual rather than explicit.

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?

"Cheaper than reading the whole graph" gives a clear selection heuristic: prefer this when you only need a single node's neighborhood. There is no explicit when-not guidance, no named alternative tool, and no statement about when a full canvas_read or a node search would be the better choice.

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.