Skip to main content
Glama
Sign In

KanbanThing

by com.kanbanthing
OverviewDiscussionsAdmin

Create a Kanban board

create_board

Create a new KanbanThing board and return its id, shareable URL and password. No sign-up. Every board is password protected: pass password to choose one, otherwise a random password is generated and returned. Give both the URL and the password to whoever should use the board. Boards are deleted when they expire.

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

Input Schema

NameRequiredDescriptionDefault
nameYesBoard name shown to everyone.
columnsNoColumns left to right after Backlog. Defaults to To Do, In Progress, Done.
passwordNoBoard password. A random one is generated and returned if omitted.
lifespan_daysNoDays until the board is deleted. Defaults to 60.

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?

Going beyond the sparse annotations (readOnlyHint false, etc.), the description discloses important behaviors: no sign-up required, password protection with automatic random generation, and automatic board deletion on expiry. This gives agents critical knowledge about side effects and security without relying on annotations.

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 compact and front-loaded with the core action and output. Every sentence adds value, covering output, security, sharing, and expiration in just three sentences without excess verbiage.

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 creation tool with no output schema, the description provides a complete picture: what it creates, what it returns, how passwords work, and when boards are deleted. It also addresses the sharing use case, making it self-sufficient for an agent to understand the tool's full lifecycle.

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?

All parameters are already documented in the schema (100% coverage), so the baseline is 3. The description adds extra meaning by explaining the password behavior (random generation if omitted) and lifespan deletion, which complements the schema rather than merely repeating it.

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 'Create' with a clear resource 'KanbanThing board' and explicitly states the return values (id, shareable URL, password). This distinguishes it clearly from sibling tools like create_card or update_card, making its purpose unambiguous.

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 description provides clear context for using the tool: creating a board doesn't require sign-up, returns a shareable URL/password, and handles expiry. However, it doesn't explicitly state when to use this tool over alternatives or exclude any sibling tools, so it stops short of full guidance.

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

All KanbanThing 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