Skip to main content
Glama
bezata

kObsidian MCP

by bezata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Outgoing Links

links.outgoing
Read-onlyIdempotent

Extracts all outbound links from a note, including wiki-style and markdown-style references. Optionally verifies if each target exists in the vault.

Instructions

Extract every link FROM a note (outbound references) — wiki-style [[…]] and markdown-style […](…). When checkValidity:true, each entry carries a valid flag indicating whether the target path resolves in the vault. Read-only. For inbound references (what points AT the note), use links.backlinks.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
vaultPathNo
checkValidityNoWhen true, each outgoing link is flagged `valid` or broken.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesList of result items; per-item shape depends on the tool.
totalYesNumber of items in `items`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.5
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed6 schema fields changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / checkValidity / description
      Added value: +"When true, each outgoing link is flagged `valid` or broken."
    • addedOutput schema / description
      Added value: +"Standard list envelope used by list/search tools."
    • addedOutput schema / properties / items / description
      Added value: +"List of result items; per-item shape depends on the tool."
    • addedOutput schema / properties / items / items / description
      Added value: +"Freeform object. The specific shape depends on the tool; see the tool description."
    • addedOutput schema / properties / total / description
      Added value: +"Number of items in `items`."
  3. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Descriptions adds meaningful behavioral context beyond the annotations: it discloses that both wiki-style and markdown-style links are extracted, that checkValidity adds a valid flag based on path resolution in the vault, and that vaultPath overrides the session-active vault. It also confirms the read-only nature, consistent with readOnlyHint and idempotentHint. No contradiction with annotations.

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 compact and well-structured. Every sentence serves a purpose: purpose, validity flag behavior, read-only confirmation, sibling alternative, and vault scoping. It front-loads the main function and keeps supporting details concise.

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?

The description is complete for a tool with an output schema that already explains return values. It details the link extraction scope, validity flag semantics, vault behavior, and explicit alternative. The references to vault.current and vault.select provide useful context without being excessive.

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 description coverage is only 33% (only checkValidity has a description). The description compensates by explaining vaultPath (overrides session vault) and checkValidity (adds valid flag). The path parameter is not explicitly described, but it's implied as the note from which links are extracted. The added semantics cover two of three parameters well, though path could have been more explicit.

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 clearly states the verb 'Extract' and the resource 'links FROM a note', specifying both wiki-style and markdown-style link formats. It explicitly distinguishes itself from the sibling 'links.backlinks' by naming the alternative and its purpose, so an agent can readily tell them apart.

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

Usage Guidelines5/5

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

The description gives explicit usage guidance: 'For inbound references (what points AT the note), use links.backlinks.' It also explains the vault scoping rule (session-active vault vs explicit vaultPath) and which argument wins. This leaves no ambiguity about when to use this tool versus alternatives.

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