Skip to main content
Glama

KanbanMCP

Turn a question into a card

promote

Turns a raised signal into a Triage card and marks the signal resolved.

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

Input Schema

NameRequiredDescriptionDefault
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

A3.5/5.0
Behavior4/5

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

Annotations declare the safety profile, but the description adds the key behavioral fact they omit: this operation creates a card AND consumes/resolves the source signal, a two-part irreversible effect. That is genuine added context beyond the structured fields, though it stops short of describing failure modes or repeat-invocation behavior.

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?

A single front-loaded sentence carrying verb, input, output, and side effect with zero filler. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating tool with no output schema, the definition covers what happens but not what is returned, whether the signal must be in a particular state, or what happens on repeat calls. Adequate but with clear gaps.

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 all three parameters are already documented and the baseline of 3 applies. The description adds no parameter-level detail and even introduces terminology drift, calling the input a 'signal' while the schema calls signalId 'the question's id.'

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?

The description names a specific transformation (raised signal → Triage card) plus a side effect (marks the signal resolved), which separates it from the plain create_card sibling. It does not explicitly name the alternatives it differs from, so it falls short of the top tier.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no mention of prerequisites (e.g. which board/persona), and no routing against siblings like create_card or resolve. Usage can only be inferred from the purpose statement.

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