Skip to main content
Glama
Sign In
Obsidian MCP Extended

Obsidian MCP Extended

by aleksakarac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_templates_tool

List available templates from a specified folder in your Obsidian vault. Works offline with native filesystem access.

Instructions

List available templates (filesystem-native, offline).

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": "list_templates_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_folderNoTemplates
vault_pathNo
ctxNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided; the description adds context about filesystem-native and offline behavior but omits details on side effects, permissions, or output format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently short but too brief to cover essential information, balancing conciseness with inadequacy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, no annotations, and minimal parameter coverage, the description fails to provide sufficient context for an AI agent to use the tool confidently.

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

Parameters1/5

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

Schema description coverage is 0% and the description does not mention any of the three parameters (template_folder, vault_path, ctx), leaving their purpose unexplained.

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 it lists available templates and specifies they are filesystem-native and offline, distinguishing it from template expansion tools.

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 usage for listing offline, filesystem-based templates but lacks explicit when-to-use or alternatives guidance, especially given siblings like expand_template_tool.

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