Skip to main content
Glama
Sign In
Obsidian MCP Wrapper

Obsidian MCP Wrapper

by UwUGreed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

read_section

Retrieve a targeted section of an Obsidian note using a handle from a prior search, enabling focused access to your vault's content.

Instructions

read_section

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

Input Schema

NameRequiredDescriptionDefault
handleYes
max_tokensNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.1/5.0
Behavior1/5

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

No annotations are provided, and the description contains no behavioral details. The agent is left without any information about side effects, permissions, pagination, or return format, making this a complete transparency failure.

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?

Although the description is short, it is under-specified rather than concise. A single word adds no value and forces the agent to rely entirely on the schema, which itself lacks descriptions. This is closer to an empty placeholder than effective conciseness.

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?

Given the nested schema, lack of output schema, and absence of annotations, the description is severely inadequate. It provides no context about what a 'section' is, how the handle works, or what the tool returns, making it nearly unusable for correct invocation.

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?

The description adds no meaning to the schema. The schema has two parameters (handle and max_tokens) with no descriptions, and schema coverage is 0%. The description does not mention parameters or how to construct them, so the agent cannot infer their purpose.

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 Guidelines1/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. The description provides no context about the intended use case, prerequisites, or situations to avoid.

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