Another bloated Obsidian MCP Server

Overview Schema Source Related Servers Discussions Admin

get_outlinks

Retrieve all outgoing links from an Obsidian note, covering both [[wikilinks]] and [markdown links]. Useful for analyzing note connections.

Instructions

Get all outgoing links from a note (both [[wikilinks]] and markdown)

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

Input Schema

Name	Required	Description	Default
`path`	Yes	Path to the note

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Aug 2, 2026

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only adds that both link types are included, but fails to explain return format, link resolution behavior, or handling of broken/self links. No output schema exists, so this gap is significant.

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?

The description is a single, front-loaded sentence that directly states the tool's action and scope without any filler or repetition.

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

Completeness3/5

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

The tool is simple with one parameter, but the absence of an output schema and any behavioral details means the description does not fully prepare the agent for what to expect. It is adequate for basic understanding but incomplete for nuanced use cases.

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 description coverage is 100%, with the 'path' parameter already described as 'Path to the note'. The description adds no new meaning beyond the schema, so it meets the baseline but does not elevate it.

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?

Description uses a specific verb ('Get'), resource ('outgoing links'), and scope ('from a note'), clearly distinguishing it from siblings like get_backlinks (incoming links) and get_link_graph (graph structure). It also specifies it returns both wikilinks and markdown links, leaving no ambiguity.

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?

The description implies usage by stating exactly what it retrieves, and the inclusion of both link types provides useful context. However, it does not explicitly mention when to avoid this tool in favor of alternatives like get_backlinks or find_broken_links, so it lacks explicit exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.