Skip to main content
Glama

clear_board

Destructive

Remove all saved drawings, shapes and text for everyone and discard pending drafts. Requires an edit link and explicit user confirmation.

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>",
      "confirm": "<confirm>"
    },
    "name": "clear_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesSet only after the user confirms clearing the board.
boardUrlYesA JotPond /b/<edit-id> or /view/<read-only-id> link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say destructiveHint=true; the description goes well beyond by disclosing that the effect is board-wide ("for everyone") and extends to "pending drafts" that the agent might not assume are at risk. It also states the authorization and confirmation requirements, which is exactly the behavioral context a destructive tool needs.

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?

Two sentences, front-loaded with the destructive effect and followed by requirements. No filler, and nothing important is buried behind trivia.

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?

For a two-parameter destructive tool with no output schema, the description covers scope, blast radius, preconditions, and confirmation policy. Nothing an agent needs in order to call it safely is missing.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: "edit link" signals that the /view/<read-only-id> form accepted by the schema will not work here, and "explicit user confirmation" reinforces the confirm const. That is genuine value beyond the field descriptions.

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?

States a specific verb and full scope: "Remove all saved drawings, shapes and text for everyone" — the word "all" plus "for everyone" clearly distinguishes it from item-level siblings like delete_item. An agent can tell what it does without opening the schema.

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?

Gives clear preconditions for use (an edit link and explicit user confirmation), which effectively rules out read-only links and unconfirmed calls. It does not explicitly name an alternative for single-item removal, but the scope word "all" implicitly routes narrow deletions elsewhere.

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