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

taskpaper-mcp-server

by kekincai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read Front TaskPaper Document

taskpaper_read_front_document

Retrieve the plain text content of the active front document in TaskPaper. Enables programmatic access to the current task list for further processing.

Instructions

Read the serialized text of the front TaskPaper document.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "taskpaper_read_front_document"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Read,' implying a non-destructive operation, but does not detail aspects like whether the document is locked during reading, permission requirements, or any side effects. The description is inadequate for a tool with zero annotation coverage.

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, concise sentence that directly states the tool's function with no extraneous words. It is front-loaded and efficient.

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?

Given no parameters and no output schema, the description is mostly complete for a simple read operation. However, it does not clarify what 'front' document means (e.g., the main document vs. a temporary view), leaving minor ambiguity. Still, it is adequate for such a simple tool.

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?

The tool has no parameters, and schema coverage is 100% (since none). The description does not need to add parameter information. Baseline for zero-parameter tools is 4; the description suffices.

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 states the tool reads the front TaskPaper document as serialized text, distinguishing it from siblings like taskpaper_read_file (reads any file) and taskpaper_list_projects (lists projects). The verb 'Read' and resource 'front TaskPaper document' are specific and unambiguous.

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. It does not mention scenarios where this tool is preferred over taskpaper_read_file or other siblings, nor does it specify any prerequisites or limitations.

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