Skip to main content
Glama
Sign In
Plumb (plumb-mcp)

Plumb (plumb-mcp)

by tathagat22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Plumb · fig node

plumb_fig_node
Read-onlyIdempotent

Read a node from a .fig file by its sessionID:localID id (from plumb_fig_outline), returning type, name, size, fills, opacity, and text details.

Instructions

Read one node from a saved .fig file by its id (the sessionID:localID form returned by plumb_fig_outline). Returns the node's type, name, size, auto-layout mode, fills, opacity, and (for TEXT nodes) characters and font. Pair with plumb_fig_outline to find the id first.

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": {
      "figPath": "<figPath>",
      "id": "<id>"
    },
    "name": "plumb_fig_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNode id — `sessionID:localID` form.
figPathYesAbsolute path to a .fig file on disk.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint true and idempotentHint true. Description adds detail about returned fields (type, name, size, etc.) and special handling for TEXT nodes, which supplements the annotations without contradiction.

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, front-loaded with action, no redundant words. Every sentence adds value.

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

Completeness5/5

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

Given only 2 simple parameters, no output schema, and no nested objects, the description covers all essential aspects: what the tool does, how to use it (pair with outline), and what it returns (list of node properties). No gaps.

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 100% with descriptions for both parameters. Description adds extra meaning by specifying the id format as 'sessionID:localID' and noting it comes from plumb_fig_outline, which is helpful beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description uses specific verb 'Read', identifies resource as 'one node from a saved .fig file', and clarifies the id format. It distinguishes from sibling tool plumb_fig_outline by stating the pairing relationship.

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?

Explicitly instructs to pair with plumb_fig_outline to find the id first, providing clear context. Does not include explicit when-not-to-use alternatives, but the context is unambiguous.

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