Skip to main content
Glama

KanbanMCP

Raise a question or note

raise
Idempotent

Files a signal: assumption (the default), question, concern, rule proposal, deferred or observation. Only blocking parks your card: keep it for a choice you cannot undo. Offer options only with type question, and mark your advice. If you are sure, act and finish the card. If not, ask a teammate in a comment with @name. Use raise only when a person must decide.

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": {
      "severity": "<severity>",
      "title": "<title>"
    },
    "name": "raise"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoThe person to ask, by name or id.
bodyNoThe facts behind the question, in a few lines. Do not paste the card.
kindNoapproval: a yes or no from a person. Use it for every yes or no, so the person sees Approve and Decline. open: any answer. Default open.
typeNoassumption, question, concern, rule (a rule proposal), deferred or observation. Default assumption, or question when you send options.
titleYesThe question as one full sentence. A person reads this first.
cardIdNoCard id, number (12) or key (WEB-12).
selectNoone: single. many: several. Default one.
boardIdNoBoard id or slug.
optionsNoThe answers you offer. Offer them for every choice. The person may still write their own.
personaNoThe persona to act as.
blockingNoPark your card until someone answers.
severityYesHow much it matters.
sessionIdNoGroups the notes from one session.
needsPersonNoOnly a person may answer.

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?

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. Beyond that, the description adds real behavioral context the annotations don't: that only blocking=true 'parks your card', that options are only valid with type question, and that recommended marks advice. It omits return behavior but adds meaningful effect disclosure.

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?

Five tight sentences with no padding, but the structure is choppy and guidance-heavy; the core definition is buried after the type enumeration rather than front-loaded, and fragments like 'Only blocking parks your card' read as notes rather than definition.

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?

There is no output schema and 14 parameters, yet the description covers only the type/options/blocking/comment trade-offs. It never addresses the two required parameters (severity, title beyond title's schema text) or what the call returns, leaving important gaps for a tool this broad.

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 the baseline is 3; the description goes slightly beyond by explaining cross-parameter semantics: 'assumption (the default)' for type, the default swap to question 'when you send options', and 'mark your advice' mapping to recommended. It does not explain the required severity values, so it doesn't fully compensate.

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 states the verb and enumerates the resource types it can file (assumption, question, concern, rule proposal, deferred, observation), and it explicitly names the sibling 'comment' it is not. However, 'Files a signal' is jargon that leaves the exact artifact (a note/question attached to a card) partly inferred rather than plainly stated.

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

Usage Guidelines5/5

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

It gives explicit when-and-when-not guidance: 'Only blocking parks your card', 'Offer options only with type question', 'If you are sure, act and finish the card. If not, ask a teammate in a comment with @name', and 'Use raise only when a person must decide.' Both the alternative actions (act/comment) and the selecting condition are named.

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