Skip to main content
Glama
ruliana

mcp-pkm-logseq

by ruliana

get_todo_list

Fetch todo tasks from your Logseq knowledge base, filterable by completion status and date range, returned as markdown.

Instructions

Retrieve the todo list from Logseq.

Use this to get a list of all the todos in the user's personal knowledge base.

Dates are expressed as:
1. today|yesterday|tomorrow|now
2. <number><unit> like 1d, 2w, 3m, 4y, 2h, 30min

Args:
    done: Whether to get the done todos or the todo todos.
    from_date (optional): The start date to filter the todos.
    to_date (optional): The end date to filter the todos.

Returns:
    A markdown formatted string containing the todos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doneNo
from_dateNo
to_dateNo
Behavior2/5

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

No annotations present, so description carries full burden. It mentions return format (markdown) and date formats but lacks details on performance, auth, or side effects.

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?

Description is structured with Args and Returns sections but could be more concise; date format explanation could be integrated into parameter descriptions.

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 tool with 3 params, no output schema, and no annotations, description covers purpose, parameters, date format, and return type adequately.

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?

Schema coverage is 0%, but description adds significant meaning: clarifies 'done' param, optional date filters, and date format conventions beyond the schema.

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?

Description clearly states the tool retrieves todo list from Logseq and distinguishes from siblings (get_personal_notes) by focusing on todos rather than notes.

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?

Description implies usage (get todos in personal knowledge base) but does not provide explicit when to use vs alternatives or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ruliana/mcp-pkm-logseq'

If you have feedback or need assistance with the MCP directory API, please join our Discord server