Skip to main content
Glama
Sign In
taskpaper-mcp-server

taskpaper-mcp-server

by kekincai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Complete TaskPaper Task

taskpaper_complete_task

Complete the first task matching a TaskPaper query. Optionally target a specific file and set the completion date.

Instructions

Mark the first item matching a TaskPaper query as done. Pass file to edit a .taskpaper file directly.

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": {
      "query": "<query>"
    },
    "name": "taskpaper_complete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
fileNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Mentions file editing but lacks detail on side effects, behavior when query matches nothing, reversibility, or other behavioral traits. Without annotations, the description carries the burden and is adequate but incomplete.

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?

Two concise sentences with no fluff. Could be slightly more efficient but well-structured and front-loaded.

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

Completeness2/5

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

Given 3 parameters, no output schema, and 8 sibling tools, the description is insufficient. Missing details on date parameter, return value, and error handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage. Only 'file' is briefly explained ('Pass file to edit a .taskpaper file directly'). No explanation for 'query' or 'date' parameters.

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?

Clearly states the verb ('mark as done') and resource ('first item matching a TaskPaper query'). Distinguishes from sibling tools like taskpaper_add_task and taskpaper_archive_done.

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?

Implies usage for completing tasks but provides no explicit guidance on when to use vs. alternatives (e.g., taskpaper_archive_done) or when not to use.

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