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

obsidian-modified-mcp-server

by marwansaab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_active_file

Retrieves the currently active file in an Obsidian vault, allowing integrations to know which note is open. Optionally specify a vault ID.

Instructions

Get the currently active file in Obsidian.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_active_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
vaultIdNoOptional vault ID (defaults to configured default vault).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.6/5.0
Behavior2/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 of behavioral disclosure. It only states the action without describing the return format, edge cases (e.g., no active file), or confirming read-only behavior. This leaves significant behavioral ambiguity.

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 does not waste words. It is front-loaded and easy to parse.

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 get tool with one optional parameter and no output schema, the description provides sufficient context for basic invocation. However, it lacks usage guidance and behavioral details, so it's not exhaustive, but adequate for the tool's 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?

The input schema has 100% coverage for the single optional vaultId parameter, which has its own description. The tool description adds no additional parameter semantics, so the baseline score of 3 applies.

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 ('Get') and a clear resource ('currently active file in Obsidian'), which distinguishes it from sibling tools like get_file_contents or open_file. It clearly states 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 description gives no explicit guidance on when to use this tool versus alternatives. The usage is implied by the name and description, but there are no exclusions or alternative suggestions, making it a 3.

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