Skip to main content
Glama
Sign In

task-board-todo-kanban

by io.github.theluckystrike
OverviewDiscussionsAdmin

Start a timer for a task

task_start_timer

Return the exact arguments to pass to the time-tracker's timer_start for one task, and record the link here. It starts nothing itself, and warns when the tracker's own project names would misfile the time.

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>"
    },
    "name": "task_start_timer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTask id, e.g. NOVA-12

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/5.0
Behavior4/5

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

The description adds behavior beyond annotations by disclosing that the tool does not start the timer itself, records a link, and issues warnings when project names would misfile time. This is especially useful because all annotations are false and say little about side effects. No contradictions with readOnlyHint false or other flags.

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 convey the function, the non-action, and the warning without filler; the operative clause is front-loaded. Every sentence earns its place.

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 single-parameter tool with no output schema and uninformative annotations, the description covers what it outputs, what it does, and a warning condition. It leaves minor gaps such as the exact shape of the returned arguments and the meaning of 'the link here,' but nothing critical blocks a call.

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 single id parameter is fully documented in the schema with 100% coverage and an example value, 'NOVA-12', so the description does not need to add much. It only reinforces 'for one task,' which adds no meaningful semantic detail 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?

The description names a specific behavior—returning exact arguments for timer_start for one task—and explicitly disambiguates from a direct timer start by saying 'It starts nothing itself.' The full scope is clear: compute args, record a link, and warn about misfiling.

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 context is implied rather than stated: the tool is meant for a single-task time-tracker invocation, and the warning hints at when it matters. There are no explicit when-to-use or when-not-to-use statements or named alternatives among siblings, so an agent must infer the selection.

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

All task-board-todo-kanban 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