Skip to main content
Glama
Sign In
Another bloated Obsidian MCP Server

Another bloated Obsidian MCP Server

by diegorv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batch_delete

Deletes multiple notes at once. Requires confirmation before proceeding, then returns per-note results.

Instructions

Delete multiple notes at once. Requires confirmation. Returns per-note success/failure results.

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": {
      "paths": "<paths>",
      "confirm": "<confirm>"
    },
    "name": "batch_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYesArray of note paths to delete
confirmYesMust be true to confirm deletion

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It discloses confirmation and per-note results, but omits details on permanence (trash vs permanent), auth, or partial failure behavior (rollback vs partial success).

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 three short, front-loaded sentences. Every sentence adds value: action, confirmation, and return behavior. No filler or redundancy.

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 simple 2-parameter tool with no output schema, the description covers the core aspects: what it does, confirmation, and return results. It could mention permanence or error handling, but overall it's nearly complete.

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

Parameters3/5

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

Schema coverage is 100% with both parameters described ('paths' and 'confirm'). The description adds no extra semantic meaning beyond the schema, only echoing the confirmation requirement.

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 'Delete multiple notes at once' uses a specific verb and resource, clearly distinguishing this batch operation from the sibling delete_note tool. It also mentions confirmation and per-note results, reinforcing the purpose.

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?

The description implies use for deleting multiple notes but does not explicitly state when to prefer this over delete_note or other alternatives. No exclusions or prerequisites beyond confirmation are mentioned.

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