Skip to main content
Glama
Sign In
Obsidian MCP Extended

Obsidian MCP Extended

by aleksakarac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

render_templater_template_tool

Render Templater templates in Obsidian by specifying a template file, with optional target file and context for dynamic content.

Instructions

Render Templater template (requires Obsidian + Templater plugin).

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": {
      "template_file": "<template_file>"
    },
    "name": "render_templater_template_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_fileYesTemplate file path
target_fileNoTarget file for context
ctxNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only mentions the plugin requirement, but does not disclose behavioral traits like side effects, output, or whether it modifies files.

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

Conciseness4/5

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

The description is efficiently short (two sentences) with no unnecessary words. However, the prerequisite could be integrated into a more comprehensive description.

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 lack of output schema and only moderate schema coverage, more context is needed. No mention of return values, errors, or what the rendered output does.

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 coverage is 67% (2 of 3 parameters described), and the description adds no parameter-level information beyond what's in the schema. No compensation for undocumented 'ctx' parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'Render Templater template' which is a verb+resource, but does not differentiate from the sibling 'expand_template_tool'. The prerequisite mention adds context but does not clarify unique purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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. The only usage hint is the prerequisite requirement, but no when-to-use or when-not-to-use information is provided.

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