Skip to main content
Glama
Sign In

McpStamp Kanban Board

by io.github.theluckystrike
OverviewDiscussionsAdmin

Delete project board

project_delete
Destructive

Delete an empty board and give its free-tier slot back. A board still holding tasks, open or done, is refused with one named, because task_add creates boards as a side effect and the work would be lost.

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": {
      "project": "<project>"
    },
    "name": "project_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesBoard to remove, e.g. 'Nova Site'. It must hold no tasks at all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already carry destructiveHint=true, but the description adds the crucial guard that only empty boards are deleted, that non-empty boards are refused, and that task_add creates boards as a side effect so deletion would lose work. This explains the real-world consequence beyond the annotation flags.

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 sentences, front-loaded main action, and each clause supports safe use. The garbled phrase 'with one named' is a clarity defect that prevents a 5.

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 one-parameter destructive tool with no output schema, this is nearly complete: purpose, refusal condition, rationale, and consequence are all present. It only misses an explicit pointer that tasks must be removed via task_delete before retrying, plus a clear statement of the success response.

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 coverage is 100% and already documents project as the board to remove with the 'must hold no tasks' constraint. The description's 'empty board' and 'free-tier slot back' add useful context but not new parameter-level meaning, so the baseline 3 applies.

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 opens with a concrete verb and object — 'Delete an empty board' — and immediately distinguishes itself from task_delete and project_list by scoping to boards and requiring emptiness. The free-tier-slot note adds context beyond the title.

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?

It clearly states the condition for use (board must be empty) and explicitly warns that non-empty boards are refused, which prevents misuse. It does not name a sibling like task_delete as the fallback for clearing tasks first, so the alternative path is implied rather than explicit.

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

All McpStamp Kanban Board toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources