taskpaper-mcp-server

Overview Schema Source Related Servers Discussions Admin

Set TaskPaper Filter

taskpaper_set_filter

Set a filter on the front TaskPaper document to show only items matching a query. Focus on specific tasks by limiting visible items.

Instructions

Set the item path filter on the front TaskPaper document.

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_set_filter"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 13, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations provided, the description must fully disclose behavior. It only states that the tool sets a filter, but omits key details: whether it replaces or appends filters, side effects on the document or UI, error states, or if the filter persists. Agents cannot predict the outcome reliably.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, but conciseness should not sacrifice necessary detail. It is adequately sized for the tool's simplicity but could include additional information within the same length without becoming verbose.

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 the low complexity (one string parameter, no output schema), the description should provide enough context for correct invocation. It fails to explain typical use cases, query syntax, or what 'item path filter' means. Agents are left to guess, reducing completeness.

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

Parameters1/5

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

The sole parameter 'query' lacks any description in the schema, and the tool description does not mention parameters at all. Schema coverage is 0%, so the description should compensate by explaining the query format or expected values, but it does not. This leaves the parameter's semantics entirely opaque.

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 indicates the tool sets an 'item path filter' on the 'front TaskPaper document', using a specific verb and resource. It distinguishes from siblings like taskpaper_search_items which performs a different action. However, the term 'filter' is not elaborated, which could be ambiguous for agents unfamiliar with TaskPaper.

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?

The description provides no guidance on when to use this tool versus alternatives such as taskpaper_search_items or taskpaper_read_front_document. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer usage without support.

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

Deploy Server