Skip to main content
Glama
Sign In
Boarderless MCP Server

Boarderless MCP Server

by CrackenReleased
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Export Board (PNG/PDF/SVG)

export_board
Destructive

Export a Boarderless canvas to PNG, PDF, or SVG. Choose format and scope to get the canvas content as a downloadable file.

Instructions

Export the current Boarderless canvas to PNG, PDF, or SVG. Requires the user to be authenticated. Returns a structured error with resolution steps if export fails.

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": {
      "format": "<format>"
    },
    "name": "export_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoExport scope. Defaults to 'canvas'.
formatYesExport format.
filenameNoOptional output filename override.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.28

TDQS

C2.9/5.0
Behavior2/5

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

The description adds a note about structured error resolution, but fails to clarify the destructive hint annotation (destructiveHint=true). Exporting typically implies no destruction, so the agent needs to know what side effects occur. The description does not disclose whether the canvas is modified or if a file is created/destroyed.

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

Conciseness4/5

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

Two concise sentences efficiently convey purpose and a key requirement (authentication) and error behavior. No extraneous words. However, it could be slightly improved by front-loading the most critical info first.

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

Completeness2/5

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

The description is incomplete given the presence of a destructiveHint annotation and no output schema. It does not explain return format (e.g., file URL, download), what 'destructive' means here, or when to use this over the sibling 'export_board_file'. The agent lacks enough context to use the tool safely and effectively.

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?

All parameters are fully described in the schema (100% coverage). The description adds no additional meaning or context beyond the schema, which already defines format, mode, and filename with enum constraints. Baseline score of 3 is appropriate.

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 clearly states the action ('Export'), the specific resource ('current Boarderless canvas'), and the target formats (PNG, PDF, SVG). This provides a clear, specific purpose. However, it does not differentiate from the sibling 'export_board_file', which likely has a different export scope or resource.

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 only mentions a prerequisite (authentication) but provides no guidance on when to use this tool vs. alternatives (e.g., 'export_board_file'). There is no mention of when-not-to-use or context for selecting this tool over siblings.

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