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

Plumb (plumb-mcp)

by tathagat22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Plumb · fig outline

plumb_fig_outline
Read-onlyIdempotent

Read a .fig file from disk to list all screens across every page. Use it to inspect or implement screens without opening Figma, requiring no plugin pairing or token.

Instructions

Read a saved .fig file from disk and list every screen (top-level frame) across every page. The headless / CI counterpart to plumb_outline — works with no Figma desktop, no plugin pairing, no FIGMA_TOKEN. Use this when you've exported a .fig file and need to inspect or implement screens without opening Figma.

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

Input Schema

NameRequiredDescriptionDefault
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 already indicate readOnlyHint=true and idempotentHint=true. The description adds behavioral context: reads from disk, lists screens across all pages, and has no external dependencies. No 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. Every phrase earns its place; no waste.

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 the tool's simplicity (one param, no output schema), the description fully covers purpose, usage, and behavior. No gaps.

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% for the single parameter figPath. The tool description does not add further parameter meaning beyond what the schema already provides. Baseline 3 is appropriate.

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?

The description clearly states the tool reads a .fig file and lists screens across pages. It distinguishes itself from sibling plumb_outline by noting it works without Figma desktop, plugin pairing, or FIGMA_TOKEN.

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

Usage Guidelines5/5

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

Explicitly specifies when to use: 'when you've exported a .fig file and need to inspect or implement screens without opening Figma.' Implicitly contrasts with plumb_outline, providing clear context and alternatives.

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