Skip to main content
Glama
Sign In
obsidian-mcp

obsidian-mcp

by ZethicTech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_links

Read-onlyIdempotent

List all outgoing links from a specified note, with options to filter by file, path, or show only the total count.

Instructions

List all outgoing links from the specified note.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoNote name (wikilink-style resolution)
pathNoExact path from vault root
totalNoShow only the total count

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds the specific behavior of listing outgoing links, which is consistent and sufficient for a simple read operation.

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 a single sentence with no waste. It could include more structural separation (e.g., bullet points) but is very concise.

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?

Without an output schema, the description could hint at the return format (e.g., list of link titles or paths). The current description is adequate but leaves some ambiguity about the output structure.

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 descriptions cover all parameters (file, path, total) clearly. The tool description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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?

The description 'List all outgoing links from the specified note' uses a specific verb (list) and resource (outgoing links) and clearly distinguishes from siblings like get_backlinks or find_unresolved_links.

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 is provided on when to use this tool versus alternatives such as get_backlinks or find_unresolved_links. There are no prerequisites or context for appropriate 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