Skip to main content
Glama
Sign In
Obsidian MCP Wrapper

Obsidian MCP Wrapper

by UwUGreed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

expand_context

Retrieves additional context from an Obsidian vault by resolving provided references, expanding the available information for the current task.

Instructions

expand_context

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

Input Schema

NameRequiredDescriptionDefault
handlesYes
max_tokensNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.3/5.0
Behavior1/5

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

With no annotations and a one-word description, there is zero disclosure of behavioral traits. The tool could be read-only, destructive, rate-limited, or stateful—nothing is communicated.

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

Conciseness2/5

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

The description is minimal but not usefully concise. It is under-specification, not efficient writing. There is no front-loaded meaning or structural benefit.

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

Completeness1/5

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

The tool has two parameters, one required, with a nested object shape, no output schema, and no annotations. The description fails to explain what 'expand_context' does, when it is appropriate, or what the parameters mean, making it completely inadequate.

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 compensate. The parameters 'handles' and 'max_tokens' are left completely unexplained, despite their complex nested structure.

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

Purpose1/5

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

Tautological: description restates name/title.

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?

There is no guidance on when to use this tool versus alternatives like get_entity_context or advisory_context. No context is provided about applicable scenarios or exclusions.

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