hive

by cmgmyr

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

todo_complete

Destructive

Mark a todo complete or reopen it with completed=false; return IDs of todos that this change newly unblocks.

Instructions

Mark a todo complete (or reopen with completed=false). Returns todo ids that this completion newly unblocked.

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": {
      "todo_id": "<todo_id>"
    },
    "name": "todo_complete"
  }
}

Input Schema

Name	Required	Description
`todo_id`	Yes
`completed`	No	Defaults to true.
`project_id`	No	Different project override. Use ONLY when the user explicitly asks for another project by name; otherwise stay in the current scope, even when results are empty.

Output Schema

Name	Required	Description	Default
`todo_id`	Yes
`completed`	Yes
`project_id`	Yes
`hive_notice`	No
`newly_unblocked`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.2.2Sep 26, 2026
- addedOutput schema / properties / hive_notice
```
Added value: +{
+  "type": "string"
+}
```
First observedv1.0.0Sep 22, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already disclose destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is largely covered. The description adds genuinely non-obvious side-effect information — that completion newly unblocks other todos and returns their ids — which an agent could not infer from structured fields.

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 short sentences, front-loaded with the primary action and the flag behavior, with the return side effect last. No wasted words.

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?

An output schema exists so return values need not be spelled out, and annotations carry the destructive/idempotency profile. The description covers the mutation, its inverse, and the unblocking side effect; only permission or scope prerequisites are unaddressed.

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 67%, and the description adds real meaning for the 'completed' flag beyond the schema's 'Defaults to true' by explaining that false reopens the todo. todo_id's semantics are left to inference, but the dual-mode explanation pushes past the baseline.

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?

States a specific verb and resource ('Mark a todo complete') plus the inverse operation ('reopen with completed=false'), which is more precise than the bare name. It does not explicitly differentiate itself from siblings like todo_update or todo_archive, so it falls short of the top score.

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

Usage Guidelines4/5

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

Explicitly tells the agent how to reopen (completed=false), which is a real usage condition, and the schema's project_id guidance covers the scope question. There is still no when-not guidance or named alternative for general todo edits, so it is clear context rather than full routing.

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