Skip to main content
Glama
idea-base-mcp-server

idea-base-mcp-server

Official

stop_working

End an open work session to record measured time automatically and clear the actively-working flag; optionally add a note or resume context before stopping.

Instructions

Stop working on a task: close your open work session with a UTC end instant, and drop the "actively working" flag (you stay assigned).

THIS IS WHAT LOGS YOUR TIME, and you supply no number. Closing the session writes the task's time entry from the session's measured worked duration — computed by the database from the recorded start and end instants, minus any waiting_on_human pause — and the response tells you the entry it wrote. Do NOT call log_time afterwards: the time is already recorded, and a hand entry on a task that already has measured time is refused. A session shorter than half a minute rounds to zero and logs nothing rather than being rounded up, and the response says so.

Requires an open session — if you have none this FAILS and writes nothing, rather than inventing a session with no start. Call start_working first.

This ENDS the session. If you are only waiting on something and intend to carry on afterwards, use pause_working instead: a pause keeps the session open and records why you stopped, which is what decides whether the interval counts as worked time.

Optionally capture your state on the way out: pass note to append a work note and/or resume_context to overwrite the resume block, so the next session can pick up where you left off.

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": {
      "task_id": "<task_id>"
    },
    "name": "stop_working"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional work note to append before stopping (what you did, what is next).
task_idYesThe ID of the task to stop working on
resume_contextNoOptional resume-context block to overwrite before stopping (current state / next steps / where to look).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.8/5.0
Behavior5/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 so: it discloses the side effect (a time entry is written from measured duration minus waiting_on_human pauses), the failure mode when no session is open ('FAILS and writes nothing'), and the edge case where sub-30-second sessions round to zero and log nothing. It also states that assignment persists after stopping.

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?

Front-loaded with the core action and the single most important fact ('THIS IS WHAT LOGS YOUR TIME'), then prerequisites, then the alternative, then optional params. It is long and uses emphasis caps plus slight redundancy in the log_time warning, but nearly every sentence adds a distinct operational fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, prerequisite, failure behavior, time-entry computation, rounding edge case, sibling disambiguation, and the meaning of every optional parameter. There is no output schema, yet the description still says what the response contains ('the response tells you the entry it wrote'), leaving nothing material for an agent to guess.

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 baseline would be 3, but the description adds real semantics: `note` *appends* a work note, `resume_context` *overwrites* the resume block, and both are applied 'on the way out' (ordering relative to session close). The rationale ('so the next session can pick up where you left off') clarifies intent beyond the schema's field text.

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?

Opens with a specific verb and effect: 'close your open work session with a UTC end instant, and drop the "actively working" flag'. It also states scope boundaries that distinguish it from siblings ('you stay assigned', 'This ENDS the session'). An agent can tell this apart from pause_working and log_time without consulting any schema.

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?

Explicitly names the alternative and the condition that selects it: 'If you are only waiting on something and intend to carry on afterwards, use pause_working instead'. It also gives a negative rule ('Do NOT call log_time afterwards') and a prerequisite ('Requires an open session... Call start_working first').

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