vaults
List Obsidian vaults accessible through the read-only MCP server.
Instructions
List known vaults.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| vault | No | Optional Obsidian vault name; defaults to OBSIDIAN_READONLY_VAULT. | |
| total | No | ||
| verbose | No |
List Obsidian vaults accessible through the read-only MCP server.
List known vaults.
| Name | Required | Description | Default |
|---|---|---|---|
| vault | No | Optional Obsidian vault name; defaults to OBSIDIAN_READONLY_VAULT. | |
| total | No | ||
| verbose | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden but only says 'List known vaults.' Does not disclose read-only nature, side effects, or any behavioral traits beyond the basic action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise (3 words), front-loaded with action. No wasted words, but may be too brief given missing details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, minimal description. Agent cannot determine return type or structure. Incomplete for a tool with multiple optional parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Description does not explain parameter purposes (total, verbose). Schema covers only vault parameter with a description. Agent cannot infer what total or verbose do.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'List known vaults' with a specific verb and resource. Distinguishes from sibling 'vault' by plural form, but does not explicitly differentiate.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like 'vault' or other listing tools. Lacks any usage context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/eothL/obsidian-readonly-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server