obsidian-modified-mcp-server

Overview Schema Source Related Servers Discussions Admin

get_file_contents

Retrieve the full content of a single file from an Obsidian vault by specifying its file path. Use this to access file contents for reading or processing.

Instructions

Returns the content of a single file in your vault.

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": {
      "filepath": "<filepath>"
    },
    "name": "get_file_contents"
  }
}

Input Schema

Name	Required	Description	Default
`vaultId`	No	Optional vault ID (defaults to configured default vault).
`filepath`	Yes	Path to the file (relative to vault root).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Jul 31, 2026

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 bears full burden. It accurately states the read-only nature ('Returns the content'), but does not disclose edge cases such as missing files, encoding issues, or size limits. It is minimal but not misleading.

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, front-loaded sentence with no filler. Every word contributes meaning, making it highly concise and readable.

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 single-file read with two well-documented parameters, the description is largely sufficient. However, the lack of an output schema means the return format (e.g., raw string, text content) is not clarified, leaving a minor gap.

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% for both parameters (vaultId and filepath), so the description adds no additional semantic value beyond what the schema already provides. Baseline 3 is appropriate.

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 uses a specific verb ('Returns') and resource ('content of a single file'), clearly distinguishing it from siblings like batch_get_file_contents or put_content. It is unambiguous about what the tool does.

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 'single file' implies a distinction from batch operations, but the description offers no explicit guidance on when to use this tool versus alternatives like batch_get_file_contents or get_heading_contents. Context is clear but exclusions are absent.

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