Skip to main content
Glama
Sign In
TaskLogger MCP

TaskLogger MCP

by khodorrrhajjj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mark_task_done

Mark a task as completed by ID, setting its status to Completed and progress to 100%.

Instructions

Shortcut: mark a task as completed (status=Completed) with 100% progress.

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": "mark_task_done"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTask numeric ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/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. It clearly states the behavioral effect (status=Completed, progress=100%) but does not mention permissions, reversibility, or possible error conditions. The disclosed behavior is transparent enough for the tool's simple scope.

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?

The description is a single, compact sentence that directly conveys the tool's purpose and effect. Every word earns its place with no redundancy.

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 one-parameter shortcut with no output schema, the description sufficiently explains the outcome. It lacks discussion of return values or edge cases, but the low complexity makes the description adequate.

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 input schema provides a full description for the id parameter (100% coverage). The description adds no extra parameter semantics, but the schema already fully documents the only parameter.

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 clearly identifies the action: marking a task as completed with 100% progress. It distinguishes itself from the generic update_task by labeling itself a 'Shortcut' and specifying the exact resulting status.

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 usage as a convenient alternative to update_task but does not explicitly state when to prefer it or mention exclusions. The context is somewhat clear but lacks direct guidance.

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

Deploy Server

Other Tools