Pinpole MCP Server

Draw nodes + connections on the Pinpole canvas

pinpole_draw_on_canvas

Draw a cloud architecture graph on a Pinpole canvas, auto-laying out nodes. Creates a project and workspace if needed, returning a live diagram URL.

Instructions

Persist an architecture graph to the user's Pinpole canvas (ReactFlow), creating a project and workspace if none is given. Returns the canvas URL to open the live diagram. Nodes are auto-laid-out left-to-right when positions are omitted.

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": {
      "graph": "<graph>"
    },
    "name": "pinpole_draw_on_canvas"
  }
}

Input Schema

Name	Required	Description	Default
`graph`	Yes
`title`	No
`projectId`	No
`workspaceId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jun 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description effectively discloses key behavioral traits: it creates project/workspace if missing, returns a canvas URL, and auto-layouts nodes left-to-right when positions are omitted. It does not mention authentication or destructive behaviors, but the provided info is sufficient for safe invocation.

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?

The description is three sentences long, front-loading the main action, then mentioning the return value, and finally an important behavioral detail. Every sentence adds value without redundancy.

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 complexity (4 parameters, nested objects, no output schema), the description adequately explains the input graph structure, side effects (creating project/workspace), auto-layout behavior, and the return URL. It provides enough context for an agent to understand the tool's purpose and usage.

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 0%, so the description must compensate. It explains the overall graph structure, auto-layout behavior, and optional project/workspace IDs, but does not detail individual parameters like node properties or edge fields beyond what the schema names imply. This adds some meaning but not a comprehensive explanation.

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 persists an architecture graph to the Pinpole canvas, distinguishing it from siblings like pinpole_build_architecture or pinpole_create_architecture which likely handle other aspects of architecture management.

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?

The description indicates when to use this tool (to persist a graph to canvas) and mentions auto-creation of project/workspace if not provided, providing clear context. However, it does not explicitly mention when not to use it or suggest alternative tools, such as pinpole_create_architecture, which might be more appropriate for initial architecture creation.

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

Deploy Server