Skip to main content
Glama

KanbanMCP

Get your context

get_context
Idempotent

Sends everything you work from again: the protocol, the workspace brief, this board's brief, your persona's brief and a digest of the rules. Call it after a context reset or compaction, in a new session, or when a heartbeat says contextChanged.

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_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardIdNoBoard id or slug.
personaNoThe persona to act as.
runtimeHandleNoA short name for this agent or sub-agent. Use a different one for each sub-agent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already carry the safety profile (destructiveHint=false, idempotentHint=true, openWorldHint=false), and the description usefully adds the trigger semantics and the fact that the bundle is re-sent whole. It does not, however, address why readOnlyHint=false for what reads as a pure retrieval, nor does it say whether persona/runtimeHandle registration has side effects. Credit for added context, but that unexplained tension keeps it at 3.

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?

Two sentences, no waste: the first front-loads what is returned, the second front-loads when to call it. Every clause earns its place and the agent gets the important information immediately.

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?

With no output schema, the description correctly carries the burden of describing the returned bundle, and it does so well. The remaining gap is default behaviour when boardId/persona/runtimeHandle are omitted (none are required) and the unexplained non-read-only hint.

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 boardId, persona and runtimeHandle are already documented in the schema. The description adds no meaning beyond that — notably it does not say what happens when all three are omitted despite required=0. Baseline 3 is correct when the schema does the heavy lifting.

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 the operation precisely and enumerates the payload — protocol, workspace brief, board brief, persona brief, rules digest — so an agent knows exactly what a call returns. It is distinguishable in content from siblings like `rules` or `get_setup`, but it never names those alternatives explicitly, so the differentiation is implicit rather than stated.

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?

It gives concrete trigger conditions: after a context reset or compaction, in a new session, or when a heartbeat reports contextChanged. That is unusually actionable. It stops short of a 5 because it never states when NOT to call it or which sibling (e.g. `rules`, `get_setup`) covers a narrower need.

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