Skip to main content
Glama

add_stroke

Draw a stroke, line or outline from [x, y, pressure] points in board coordinates. Pressure ranges from 0 to 1. Requires an edit link; changes appear live.

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": {
      "boardUrl": "<boardUrl>",
      "points": "<points>"
    },
    "name": "add_stroke"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
colorNo#1f2937
pointsYes
boardUrlYesA JotPond /b/<edit-id> or /view/<read-only-id> link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds real context on top: an edit-link authorization requirement and that "changes appear live" to other viewers. That is exactly the kind of operational detail annotations cannot carry; only the size/color defaults and any rate/point limits remain undisclosed.

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?

Three short sentences, front-loaded with the action and the point format, then the constraint. Minor redundancy in "stroke, line or outline," but nothing that costs the reader.

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

Completeness3/5

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

The core of a mutation tool is covered: what it draws, the coordinate and pressure units, and the authorization prerequisite. For a write tool with no output schema, the description never indicates what comes back (e.g., an item id needed for a later delete_item call), and the styling parameters are unexplained.

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 only 25%, so the description must compensate, and it does so for the most complex parameter by spelling out the three-element point tuple and the 0-1 pressure scale. It says nothing about the `size` or `color` parameters, leaving two of four under-documented across both sources.

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?

States a specific verb and resource ("Draw a stroke") and names the exact input representation ([x, y, pressure] points in board coordinates), which lets an agent distinguish it from add_text or clear_board. It stops short of explicitly contrasting with those siblings, but the resource is unambiguous.

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

Usage Guidelines3/5

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

Implies usage through the prerequisite "Requires an edit link," which tells the agent a read-only board link will not work. There is no explicit when-to-use versus add_text (both draw on a board) and no guidance on when a freehand stroke is preferred over text.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources