Skip to main content
Glama

KanbanMCP

Check or report your rules

rules

Keeps your installed rules in step. With ruleId, it records where you installed a rule and its hash. Call it once per file after you install a rule from get_setup (part "rules"). Without ruleId, it tells you which rules you hold are stale. Pass their ids and hashes before you finish work or after a sync.

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

Input Schema

NameRequiredDescriptionDefault
hashNoThe rule's hash, as delivered.
pathNoWhere you wrote it.
rulesNoWithout ruleId: the rules you installed, id and hash.
clientNoYour tool's name.
ruleIdNoThe rule's id. Give it to record where you installed it.
boardIdNoBoard id or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations establish the safety profile (not read-only, not idempotent, not destructive), so the bar is lower. The description still adds real behavioral value by spelling out the conditional logic (with/without ruleId) and the persistence effect ("records where you installed a rule and its hash"). It doesn't detail what happens on repeated calls or auth requirements, hence not a 5.

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?

Four compact sentences with the two-mode structure front-loaded after the opener. Little waste, though the leading metaphor consumes a sentence that could carry more direct information.

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 mutation tool with no output schema, the description covers both input modes, the workflow trigger points, and roughly what the non-recording mode returns (which rules are stale). It leaves some gaps around the response shape and repeated-call behavior, but is largely sufficient to invoke correctly.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining the conditional semantics of ruleId (record install) versus omitting it (report stale), and by clarifying how the rules/hash/path payload is used together. This is meaningful added meaning over the field-level descriptions.

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 a specific resource (installed rules) and clarifies two distinct modes - recording an install with ruleId versus reporting stale rules without it. It differentiates itself by linking to the sibling get_setup (part "rules"). The opening metaphor "keeps your installed rules in step" is slightly vague, but the following sentences pin down the actual operation.

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?

Gives explicit timing for both branches: "Call it once per file after you install a rule from get_setup" and "Pass their ids and hashes before you finish work or after a sync." This is clear when-to-use guidance tied to workflow events. It stops short of stating exclusions or when not to call it, so it falls just below a 5.

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