Skip to main content
Glama
Sign In
Pinpole MCP Server

Pinpole MCP Server

by codeforstartups
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get the canvas URL for a workspace

pinpole_open_canvas

Open a live, editable architecture diagram in your browser from Pinpole by providing project and workspace IDs.

Instructions

Return the Pinpole canvas deep link for a project + workspace so the user can open the live, editable architecture diagram in their browser.

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

Input Schema

NameRequiredDescriptionDefault
projectIdYes
workspaceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden. It states the tool returns a link, implying a read-only operation, but does not disclose side effects, authentication requirements, or rate limits.

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 a single, focused sentence that clearly states the purpose without unnecessary words. It is front-loaded with the key action and outcome.

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?

Considering the tool's simplicity (two parameters, no output schema, no annotations), the description is nearly complete. It could mention that a URL is returned, but the purpose is sufficiently clear.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only mentions 'project + workspace' without explaining the parameters in detail. It adds minimal meaning beyond the schema, failing to compensate for the lack of descriptions in the 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?

The description clearly states the tool returns a canvas deep link for a specific project and workspace, enabling the user to open the live diagram. It uses a specific verb ('Return') and resource ('canvas deep link'), distinguishing it from siblings like pinpole_draw_on_canvas.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives. It does not mention when not to use it or compare with sibling tools such as pinpole_create_architecture.

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