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

taskpaper-mcp-server

by kekincai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search TaskPaper Items

taskpaper_search_items

Search TaskPaper files or open projects using queries like 'not @done' or '/project Inbox//*' to filter tasks.

Instructions

Search TaskPaper items. Pass file to search 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_search_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
queryYesTaskPaper query, for example "not @done" or "/project Inbox//*"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It doesn't state that search is read-only, case sensitivity, or return format. Minimal behavioral info.

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?

Single sentence, no wasted words. Could be slightly more structured, but it is appropriately sized.

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?

No output schema, so description should explain return format. It doesn't. Also lacks details on search scope behavior when file is omitted.

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?

Schema coverage is 50% (only query has description). The description adds context for the file parameter ('pass file to search...'), which is useful. Query description includes a helpful example.

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?

The description clearly states the tool searches TaskPaper items. The name and title reinforce this. It distinguishes from siblings by being the only search tool, though no explicit differentiation is made.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The mention of passing a file is the only usage hint; no when-not or alternative tool references.

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