Skip to main content
Glama
Sign In
kanbn-mcp

kanbn-mcp

by kjduling
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kanbn_current_user

Identify the active Kanbn user by checking KANBN_USER, then falling back to git email/name when contributors are declared.

Instructions

Resolve the current user (KANBN_USER, then git email/name when contributors are declared).

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

Input Schema

NameRequiredDescriptionDefault
pathNoPath to the project root directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of explaining behavior. It discloses the resolution algorithm and precedence, which is valuable behavioral detail. It does not describe the return format or what happens if no user can be resolved, but the core resolution behavior is transparent.

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?

The description is a single, well-structured sentence that front-loads the action and parenthetically provides the key resolution detail. No redundant words or repetition of schema content.

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 simple one-parameter tool this is mostly sufficient, but the phrase 'when contributors are declared' is ambiguous and the return value is not described. There is no output schema to fill that gap, so the description could be slightly more explicit.

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?

The schema already fully documents the only parameter, 'path', as the project root directory. The description adds no additional parameter meaning, so the baseline of 3 applies given 100% schema coverage.

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 clearly identifies the tool's purpose: resolving the current user with a specific precedence order (KANBN_USER, then git email/name). It is concise and distinct from sibling tools like kanbn_get_contributors, though it does not explicitly contrast itself with them.

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?

The description provides no guidance on when to use this tool versus alternatives such as kanbn_get_contributors or kanbn_find_contributor. The condition 'when contributors are declared' hints at context but does not clarify when this tool is preferred over sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools