Skip to main content
Glama

KanbanMCP

Get set up

get_setup
Read-onlyIdempotent

Your first call on a new connection. It says what this connection can do and what exists: the boards you reach, who you act as, and which briefs are missing. It gives the steps to set yourself up and the questions to ask. Part "rules" returns the exact rule and skill to install. Part "briefs" returns how to write the briefs.

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": "get_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
partNorules or briefs. Leave it out for the setup steps.
boardIdNoThe board the rules are for (id or slug), on a workspace link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnly, idempotent, closed-world, non-destructive), so the description's added value is spelling out the content surfaced per mode. It tells the agent what 'rules' and 'briefs' parts return, which is context annotations cannot convey.

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?

Front-loaded with the key fact that it is the first call, and each subsequent sentence maps to a concrete return group. Slightly prose-heavy with some restatement ('what this connection can do and what exists'), but no wasted sentences.

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?

No output schema exists, yet the description sketches what each mode returns and what the default call returns, which is the critical missing piece for an orientation tool. Annotations carry the safety profile, leaving nothing essential unstated.

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 both parameters are documented at baseline. The description goes further by explaining what each `part` value actually yields ('exact rule and skill to install' vs 'how to write the briefs'), adding semantic depth beyond the schema's short enum note.

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 role ('Your first call on a new connection') and enumerates what it surfaces: reachable boards, acting identity, missing briefs. It is clearly differentiated by being the orientation entry point, though it never names which sibling it supersedes (e.g., get_context or list_boards).

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?

Explicitly frames the prime usage condition ('first call on a new connection') and explains what each `part` value is for, which routes the agent correctly. It stops short of any when-not-to-use or alternative guidance.

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