Skip to main content
Glama
Sign In
obsidian-modified-mcp-server

obsidian-modified-mcp-server

by marwansaab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batch_get_file_contents

Retrieve the contents of multiple files from an Obsidian vault in a single operation, with each file's content preceded by a header for clarity.

Instructions

Return the contents of multiple files concatenated with headers.

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": {
      "filepaths": "<filepaths>"
    },
    "name": "batch_get_file_contents"
  }
}

Input Schema

NameRequiredDescriptionDefault
vaultIdNoOptional vault ID (defaults to configured default vault).
filepathsYesList of file paths to read (relative to vault root).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the observable behavior of concatenating contents with headers, but does not explicitly state that it is read-only, how errors are handled, or what the header format looks like. The read-only nature is implied but not explicitly stated.

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 front-loads the core purpose. Every word earns its place with no redundancy or filler.

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 batch read tool with two well-documented parameters and no output schema, the description covers the essential return formatting (headers, concatenation). It could mention behavior on missing files or an explicit alternative to get_file_contents, but overall it's sufficient for a tool of this complexity.

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 description coverage is 100%, with both vaultId and filepaths adequately described in the input schema. The description adds no additional parameter details, which is acceptable given the schema's thoroughness.

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 a specific action ('Return the contents') and resource ('multiple files') with a distinctive behavior ('concatenated with headers'). This differentiates it from sibling tools like get_file_contents, which handles a single file.

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 phrase 'multiple files' implies the tool is for batch reading, which provides some context. However, there is no explicit mention of when to use this instead of get_file_contents or other alternatives, nor any exclusions or prerequisites.

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