Skip to main content
Glama
bezata

kObsidian MCP

Search Tasks

tasks.search
Read-onlyIdempotent

Scan an Obsidian vault for markdown tasks and filter by status, priority, due date, recurrence, or tag. Results include task text, source location, and metadata for further manipulation via toggle or update.

Instructions

Scan the vault for Tasks-plugin-style markdown task lines (- [ ] / - [x]) and filter by status, priority, due date range, recurrence, or tag. Result items include the task text, source file, line number, status, and parsed metadata — enough to locate and further manipulate each task via tasks.toggle or tasks.updateMetadata. sortBy controls ordering; limit caps the result count. Read-only. For vault-wide counts without per-task detail, use tasks.stats.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo`incomplete` = open tasks `[ ]`; `completed` = done `[x]`; `all` = both.
priorityNoTasks-plugin priority level.
dueBeforeNoOnly tasks due strictly before this ISO date.
dueAfterNoOnly tasks due strictly after this ISO date.
dueWithinDaysNoOnly tasks due within N days of today (inclusive).
hasRecurrenceNoFilter to recurring (or non-recurring) tasks.
tagNoOnly tasks that carry this tag (leading `#` stripped).
sortByNoResult ordering. Default: file then lineNumber.
limitNoCap the number of results. Default: 500.
vaultPathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesNumber of items in `items`.
itemsYesList of result items; per-item shape depends on the tool.
Behavior5/5

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

Annotations already signal read-only/idempotent, and the description reinforces with 'Read-only'. It details result contents (text, source file, line number, metadata), sortBy/limit effects, and scope behavior, adding significant value beyond annotations.

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?

Two efficient paragraphs: first covers core purpose, filters, output, and related tools; second explains vault scoping. No redundant sentences, all earn their place.

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

Completeness5/5

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

Given 10 parameters, high schema coverage, annotations, and output schema, the description covers all essential aspects: what it searches, filter options, output fields, ordering, limit, related tools, and vault path. Default limit is mentioned. Complete for its context.

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 90%, so baseline 3. The description adds context by grouping filter types (status, priority, due date, recurrence, tag) and explaining the output shape, which helps the agent understand parameter relationships beyond individual schema descriptions.

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 scans for Tasks-plugin markdown task lines and filters by various criteria, distinguishing it from siblings like tasks.stats (counts) and notes.search (general notes). The verb 'scan' and resource 'tasks' are precise.

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

Usage Guidelines5/5

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

Explicitly contrasts with tasks.stats for vault-wide counts, mentions tasks.toggle/tasks.updateMetadata for subsequent actions, and clarifies vault scope (session-active or explicit vaultPath). Provides clear when-to-use guidance.

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/bezata/kObsidian'

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