Skip to main content
Glama

KanbanMCP

Set a brief

set_brief
DestructiveIdempotent

Replaces a brief: this board's brief, or with scope workspace the workspace brief that every board's agents read. Use it only after the person sees the draft and says yes. How to write it: call get_setup with part "briefs".

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

Input Schema

NameRequiredDescriptionDefault
bodyYesThe whole brief, in markdown. It replaces the old one.
scopeNoboard (the default) or workspace.
boardIdNoBoard id or slug.
personaNoThe persona to act as.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the blast-radius fact that a workspace-scoped brief is what 'every board's agents read' and that the body 'replaces the old one' — non-obvious impact beyond the hints. It does not contradict the annotations; it reinforces them.

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?

Three short sentences, each load-bearing: the scope/replacement semantics lead, the human-approval precondition follows, and the drafting pointer closes. No filler, front-loaded.

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 destructive mutation tool with annotations covering safety and no output schema, the description covers the destructive/overwrite nature, the scope-dependent blast radius, and the approval precondition. Nothing needed to invoke it correctly is missing.

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, but the description adds real meaning for scope by explaining the workspace value's cross-board effect rather than just restating the enum. It doesn't expand on boardId or persona, keeping it just above baseline.

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?

Names a specific verb (replaces) and resource (brief), and immediately distinguishes the two scopes: the board's brief vs. 'with scope workspace the workspace brief that every board's agents read.' An agent can tell this apart from sibling tools like update_card or get_setup 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 Guidelines5/5

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

Gives an explicit precondition ('Use it only after the person sees the draft and says yes') and routes the agent to another tool for the drafting workflow ('call get_setup with part "briefs"'). When-to-use and the prerequisite step are both stated, not inferred.

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