Skip to main content
Glama

KanbanMCP

Answer or close a question

resolve

Closes a question. With answer, it answers a teammate's question when you know the answer. Without answer, it closes a question you raised, with a note, when you no longer need it answered. Only a person may close a question that has needsPerson. A card parked on it returns to Ready.

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

Input Schema

NameRequiredDescriptionDefault
noteNoWithout answer: why you no longer need an answer.
answerNoThe answer. Needs Worker. Leave it out to close your own question.
boardIdNoBoard id or slug.
personaNoThe persona to act as.
signalIdYesThe question's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Adds real context beyond the annotations: the authorization constraint ('Only a person may close a question that has needsPerson') and the side effect ('A card parked on it returns to Ready'). Annotations only declare the generic mutation profile (readOnly=false, destructive=false, idempotent=false), so this disclosure is genuinely additive, though error behavior is not covered.

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-loads the core action, then walks through each mode in order; nearly every sentence carries a distinct rule. Slightly dense with four clauses packed into the first two sentences, but nothing is wasted.

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 non-idempotent mutation with no output schema, the description covers both operating modes, the permission gate, and the downstream card-state effect. What remains unstated (failure modes, whether the question is re-openable) is minor.

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 100%, so the baseline is 3. The description restates the answer/note conditional that the schema already documents, adding only mild framing rather than new syntax, formats, or constraints for boardId, persona, or signalId.

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+resource ('Closes a question') and immediately splits into the two distinct operations it performs: answering a teammate's question vs closing your own. An agent can distinguish this from siblings like raise and comment 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?

Explicitly gives the selection rule between the two modes: supply 'answer' when you know the answer to someone else's question, omit it and pass a note when closing your own. No alternatives (e.g. raise, comment) are named, so it stops short of full routing 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