Skip to main content
Glama
the-real-talk

the-real-talk

get_nodes_bindings

Read values, variable bindings, fills, and strokes for every node under a root to a chosen depth, with field filters and cursor-based pagination for large trees.

Instructions

Read, for every node under rootId down to depth (0 = the root alone), its values, its variable bindings with the variable name ({id, name}), its fills and its strokes (color, bound variable). Instance children are excluded (instanceChildrenExcluded and childrenCount tell). fields limits values and bindings to those fields (default: all of: height, width, characters, itemSpacing, paddingLeft, paddingRight, paddingTop, paddingBottom, visible, topLeftRadius, topRightRadius, bottomLeftRadius, bottomRightRadius, minHeight, maxHeight, minWidth, maxWidth, strokeWeight, strokeTopWeight, strokeRightWeight, strokeBottomWeight, strokeLeftWeight, opacity, counterAxisSpacing, fontFamily, fontSize, fontStyle, fontWeight, letterSpacing, lineHeight, paragraphSpacing, paragraphIndent). Large volumes come in pieces: maxNodes per call (default 500); PARTIAL with nextCursor when the budget or maxNodes is reached.

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": {
      "rootId": "<rootId>",
      "depth": "<depth>"
    },
    "name": "get_nodes_bindings"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthYes
cursorNonextCursor of a previous PARTIAL answer, to continue where it stopped
fieldsNo
rootIdYes
maxNodesNo
timeBudgetMsNoTime budget of the plugin for this call in ms (default 60000, max 100000). When it is reached the answer says it is PARTIAL and gives nextCursor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does reasonably well: it discloses that instance children are excluded (with instanceChildrenExcluded/childrenCount as signals), that results can be PARTIAL with a nextCursor when a node budget or time budget is hit, and gives the maxNodes default of 500. It stops short of describing output shape or costs beyond volume, but the main behavioral surprises are surfaced.

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

Conciseness3/5

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

The critical information is front-loaded, but the middle of the paragraph spends a large share of its length enumerating ~33 field names that already appear as an enum in the schema. That enumeration bloats the description without adding decision-relevant meaning, and the single dense paragraph makes the pagination contract easy to skim past.

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?

Six parameters, no output schema, and no annotations make this a fairly complex tool, yet the description covers scope, exclusion rules, field filtering, volume limits and pagination sufficiently for an agent to call it correctly and handle partial results. It could go further on how to resume and what a complete vs partial answer looks like, but nothing essential is missing.

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

Parameters4/5

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

Schema coverage is only 33%, and the description compensates by explaining depth 0 semantics, the meaning of fields (limits values and bindings), the maxNodes default and the PARTIAL/cursor continuation contract. The long list of default fields mostly duplicates the schema enum and even conflicts with the schema's stated default of [], which slightly muddies rather than clarifies.

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 opens with a specific verb and resource ('Read, for every node under rootId down to depth') and enumerates what is returned: values, variable bindings with variable name, fills and strokes. It is clearly distinct from a single-node read, though it does not name a sibling tool to reinforce the contrast.

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 through the scope description and the pagination note. There is no explicit statement of when to prefer this over get_nodes_info, get_node_info or audit_bindings, nor any prerequisites. Adequate but leaves the alternative-selection decision to inference.

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

Deploy Server

Other Tools