ontology-atlas

Overview Schema Source Related Servers Discussions Admin

find_backlinks

Read-only

Find every node that points to a target slug by scanning frontmatter arrays and body wikilinks, so AI agents can trace graph dependents.

Instructions

Return every node that points to the target slug. Scans both frontmatter array keys (capabilities / elements / dependencies / relates / contains / describes etc.) and the wikilinks / markdown links in the body. Used by AI agents to walk the graph from a node to its dependents.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Target vault-relative slug (omit the .md extension).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`target`	Yes
`matches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.4.0Oct 1, 2026

addedOutput schema / properties / matches / items / oneOf

Added value: +[
+  {
+    "properties": {
+      "isNode": {
+        "const": true
+      }
+    },
+    "required": [
+      "kind"
+    ]
+  },
+  {
+    "not": {
+      "anyOf": [
+        {
+          "required": [
+            "uid"
+          ]
+        },
+        {
+          "required": [
+            "kind"
+          ]
+        }
+      ]
+    },
+    "properties": {
+      "isNode": {
+        "const": false
+      }
+    }
+  }
+]

addedOutput schema / properties / matches / items / properties / ambiguousTail
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / matches / items / properties / isNode

Added value: +{
+  "description": "True when the referrer is a graph node (has `kind:`). False for a wiki page or other Markdown that links to the target; such a row carries neither `uid` nor `kind`.",
+  "type": "boolean"
+}

addedOutput schema / properties / matches / items / properties / uid / description

Added value: +"The referring node's permanent UID. Absent when that node has no valid `uid:` (validate_vault reports it) and on every non-node row."

changedOutput schema / properties / matches / items / required

Previous value: -[
-  "uid",
-  "slug",
-  "kind",
-  "title",
-  "mtime"
-]New value: +[
+  "slug",
+  "isNode",
+  "title",
+  "mtime"
+]

First observedv0.13.0Sep 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful behavioral scope beyond them: it enumerates that frontmatter array keys (capabilities/elements/dependencies/etc.) AND body wikilinks/markdown links are scanned, which tells the agent exactly what counts as a backlink.

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?

Three short sentences, front-loaded with the core behavior and followed by the scanning scope and use case. No filler, though the third sentence is closer to rationale than operational guidance.

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

Completeness4/5

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

An output schema exists, so return-value explanation is unnecessary. The description covers the scan sources and directionality, leaving only explicit sibling routing unaddressed, which is a minor gap for a single-param read tool.

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 coverage is 100% and the single 'slug' param is already documented in the schema (vault-relative, omit .md). The description adds no extra syntax or format detail beyond that, so the baseline 3 applies.

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?

States a precise verb+resource+direction: 'Return every node that points to the target slug.' The inbound-edge semantics clearly distinguish it from siblings like find_neighbors (neighbors) and find_path (paths) without needing to name them.

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

Usage Guidelines3/5

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

'Used by AI agents to walk the graph from a node to its dependents' implies an intended use context, but it never states when to pick this over find_neighbors or find_path, nor any exclusion conditions. Usage is only inferred, not guided.

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