Skip to main content
Glama
Sign In
Another bloated Obsidian MCP Server

Another bloated Obsidian MCP Server

by diegorv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

apply_template

Process a template with variables and return the substituted content without creating a file. Supports placeholders for title, date, time, and custom variables.

Instructions

Apply a template with variables and return the processed content without creating a file. Supports {{title}}, {{date}}, {{date:FORMAT}}, {{time}}, and custom {{variable}} placeholders.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the template
titleNoTitle to replace {{title}} placeholder
variablesNoCustom variables as key-value pairs (e.g., {"author": "John"})

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.5/5.0
Behavior4/5

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

Discloses key behavioral traits: no file creation, returns processed content, and supports specific placeholder syntax. Since no annotations are provided, these details carry the full burden and are well covered, though error handling is not mentioned.

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?

Single sentence, front-loaded with the main action and outcome, with no wasted words. Efficiently conveys purpose, behavior, and placeholder support.

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

Completeness5/5

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

For a template processing tool, the description is complete: defines inputs, output, and side effects (none). The 'without creating a file' note differentiates it from sibling create_from_template, covering the needed context.

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

Parameters4/5

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

Schema already covers all parameters with descriptions, and the description adds meaningful context about placeholder transformation (e.g., {{title}}, {{date:FORMAT}}, custom {{variable}}), enriching the semantic understanding of the 'variables' parameter.

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?

States 'Apply a template with variables' with a specific verb and resource, and explicitly says it returns processed content without creating a file, distinguishing it from siblings like create_from_template.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context via 'without creating a file', implying it is for processing/previewing rather than file creation, but does not explicitly name alternative tools or conditions for non-use.

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