Skip to main content
Glama
Sign In

McpStamp Kanban Board

by io.github.theluckystrike
OverviewDiscussionsAdmin

Log time on a task

task_log_time

Add real minutes worked to one task so estimate and actual can be compared. Minutes ADD; a negative corrects an over-count. Below zero or past 100,000 is refused. This counter is the board's own.

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": {
      "id": "<id>",
      "minutes": "<minutes>"
    },
    "name": "task_log_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTask id, e.g. NOVA-12
minutesYesMinutes to add; a negative number corrects an over-count

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond annotations: explains that minutes are incremental, that negatives correct over-counts, that values outside -100000..100000 are refused, and that the counter is scoped to the board. This is critical behavioral context the annotations do not convey.

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 sentences, each earning its place: purpose, add/correct semantics, and bounds/scope. No filler or redundancy. Front-loaded with the core action.

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?

Complete for a simple two-parameter mutation tool: it covers purpose, mechanics, bounds, and scope. It doesn't describe the success response, but no output schema exists and the additive behavior makes the outcome self-evident. Minor gap: no mention of prereq such as task existence, but that's implied by 'task id'.

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 coverage is 100% and the schema already describes 'Minutes to add; a negative number corrects an over-count'. The description adds the real-worked context and board scope but does not materially extend parameter meaning beyond the schema.

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?

States a specific verb and resource: 'Add real minutes worked to one task'. It explains the purpose (estimate vs actual comparison) and clarifies the additive semantics, which distinguishes it from other task mutation tools like task_start_timer or task_update.

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

Usage Guidelines3/5

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

The description implies when to use it (to log actual time worked against a task) but never explicitly names alternatives or says when not to use. Sibling tools like task_start_timer and task_update exist, but the description doesn't guide selection between them beyond purpose.

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

All McpStamp Kanban Board toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources