Skip to main content
Glama
bezata

kObsidian MCP

by bezata
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Toggle Task Status

tasks.toggle

Toggle a task's checkbox state in a specified note line, adding a completion date when marked done.

Instructions

Flip a task line between [ ] and [x] in place, identified by sourceFile and 1-based lineNumber. When marking a task done, a ✅ YYYY-MM-DD date is stamped into the line (default today; override with doneDate). Fails if the target line is not a task checkbox. Use tasks.search to find the right sourceFile/lineNumber pair.

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
doneDateNoWhen marking a task done, stamp this date into the `✅ YYYY-MM-DD` metadata. Defaults to today.
vaultPathNo
lineNumberYes1-based line number of the task line.
sourceFileYesNote containing the task.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesThe path or identifier the tool acted on.
changedYesTrue if the tool altered vault state on this call; false if it was a no-op.
summaryYesShort human-readable summary of what happened.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.3.5
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed8 schema fields changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / doneDate / description
      Added value: +"When marking a task done, stamp this date into the `✅ YYYY-MM-DD` metadata. Defaults to today."
    • addedInput schema / properties / lineNumber / description
      Added value: +"1-based line number of the task line."
    • addedInput schema / properties / sourceFile / description
      Added value: +"Note containing the task."
    • addedOutput schema / description
      Added value: +"Standard mutation envelope. Individual tools may attach additional fields (e.g. `created`, `appended`, `before`/`after` counts) — those are documented in the tool description."
    • addedOutput schema / properties / changed / description
      Added value: +"True if the tool altered vault state on this call; false if it was a no-op."
    • addedOutput schema / properties / summary / description
      Added value: +"Short human-readable summary of what happened."
    • addedOutput schema / properties / target / description
      Added value: +"The path or identifier the tool acted on."
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond annotations (destructiveHint=false, readOnlyHint=false), the description discloses key behaviors: in-place editing, the date-stamping side effect with default and override, and the failure condition when the line is not a task. No contradiction with 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?

The description is compact, front-loaded with the core action, and every sentence adds value: main operation, date stamp detail, failure condition, and vault selection rule. No waste.

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?

Covers essential operation, failure mode, vault handling, and how to obtain inputs. Since an output schema exists (though not provided), return values are likely covered there. The description is sufficiently complete for an agent to call correctly.

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 covers 75% of parameters with descriptions. The description adds meaning to doneDate (default today, override) and clarifies vaultPath's precedence. It complements the schema adequately, leaving only vaultPath's format undefined but its role clear.

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 states a specific verb ('Flip'), a resource (task line), and precise identifying parameters (sourceFile and 1-based lineNumber). It clearly distinguishes from siblings like tasks.search (find) and tasks.create (make new), and the phrase 'in place' clarifies mutation vs. creation.

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

Usage Guidelines4/5

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

Explicitly directs agents to use tasks.search to find the right sourceFile/lineNumber pair, which is actionable guidance for correct invocation. It also explains the vault selection rule (active vault vs explicit vaultPath). It does not explicitly state when NOT to use the tool, but the search pointer serves as an effective alternative.

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