sketchflow-mcp

Overview Schema Source Related Servers Discussions Admin

open_board

Launch the SketchFlow sketch board in the user's browser if it is not already open and return its address and status.

Instructions

Open the SketchFlow sketch board in the user's browser (if it is not already open) and report its address and status. Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_board"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0-beta.1Nov 6, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool opens a browser view and reports address and status, plus a conditional no-op behavior when already open, but it does not describe permissions, side effects beyond opening, or output details beyond 'address and status'.

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 compact sentence plus the useful ordering instruction 'Call this first.' It is front-loaded and contains no redundant wording.

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?

For a zero-parameter opener with no annotations or output schema, the description covers the key behavior: opening the board, avoiding reopening if already open, reporting address and status, and calling it first. The only gap is that 'status' is not elaborated.

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?

The tool has zero parameters, so there is no parameter semantics to explain. The description appropriately avoids inventing irrelevant parameter guidance.

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 uses a specific verb and resource: open the SketchFlow sketch board in the user's browser. It also clarifies reporting behavior and ordering, making it distinguishable from sibling tools like draw, edit_items, and look.

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 instruction 'Call this first' gives clear sequencing guidance, and the conditional 'if it is not already open' clarifies when opening is needed. It does not name alternatives or explicit exclusions, but the intended usage context is clear.

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