idea-base-mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

quick_log

Record finished work in one call: create a task, mark it done, and log measured minutes. Use it only for work whose duration you already observed.

Instructions

Quick workflow for recording work that is ALREADY FINISHED: creates a task, marks it done, and logs time in one call.

minutes must be MEASURED time, not an estimate. This is a hand-entry path — there is no work session behind it — so only use it for work you actually observed the duration of, and prefer start_working / stop_working whenever the work is still ahead of you, because stop_working writes the time entry from the measured session and you type no number at all.

An estimate goes in estimated_minutes, which is a separate optional argument here precisely so the two cannot be the same number by accident. Omit it and it defaults to minutes, as before.

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": {
      "project_id": "<project_id>",
      "title": "<title>",
      "minutes": "<minutes>"
    },
    "name": "quick_log"
  }
}

Input Schema

Name	Required	Description
`notes`	No	Notes about what was done during this time (optional, defaults to description if not provided)
`title`	Yes	Title of the completed task
`minutes`	Yes	Minutes you MEASURED spending on this work. Must be positive. Not an estimate — that is estimated_minutes.
`project_id`	Yes	The ID of the project to add the task to
`description`	No	Detailed description of the task (optional)
`estimated_minutes`	No	What the task was ESTIMATED to take, if that is a different number from what it actually took (optional). Defaults to `minutes`.
`acceptance_criteria`	No	Criteria for task completion (optional)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.10.0Nov 10, 2026

addedInput schema / properties / estimated_minutes

Added value: +{
+  "description": "What the task was ESTIMATED to take, if that is a different number from what it actually took (optional). Defaults to `minutes`.",
+  "type": "number"
+}

changedInput schema / properties / minutes / description

Previous value: -"Number of minutes spent on this work"New value: +"Minutes you MEASURED spending on this work. Must be positive. Not an estimate — that is estimated_minutes."

First observedv1.2.0Aug 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the side-effect bundle (task creation + completion + time entry) and the defaulting behavior of estimated_minutes. It stops short of stating permission requirements, whether the created task is retrievable/rollback-able, or what the response contains.

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?

The composite action and the measured-vs-estimated distinction are front-loaded and the paragraphs are short. Minor waste in the trailing 'as before', which references history the calling agent does not have.

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 7-parameter mutation tool with no annotations and no output schema, the description covers the critical trap (measured vs estimated time) and the alternative workflow. The main residual gap is what the call returns and whether partial failure can leave a task created without a time entry.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond it: minutes is a measured value rather than an estimate, and estimated_minutes exists as a separate argument specifically to prevent the two collapsing to the same number. That is a semantic constraint the schema alone does not convey.

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 concrete composite action — 'creates a task, marks it done, and logs time in one call' — for work that is 'ALREADY FINISHED'. That scope statement distinguishes it from single-purpose siblings like create_task, log_time, or stop_working without needing their schemas.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use condition (work already finished, duration actually observed) and an explicit when-not-to / alternative ('prefer start_working / stop_working whenever the work is still ahead of you'), plus the reason the alternative is better (stop_working writes the entry from the measured session).

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