Edgepedia

Connect two Edgepedia articles

connect

Read-onlyIdempotent

Find the shortest chain of in-text links from one Edgepedia article to another (at most 6 hops), with the sentence that makes each hop; pass two ids as search returns them.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	Yes	The target article, named the same ways.
`from`	Yes	The starting article's id (such as "koala"), its ep… id, or its title.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`to`	Yes
`from`	Yes
`hops`	No
`path`	No
`text`	Yes
`found`	Yes
`steps`	No
`reason`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

changedInput schema / properties / from / description

Previous value: -"The starting article's id (such as \"koala\")."New value: +"The starting article's id (such as \"koala\"), its ep… id, or its title."

changedInput schema / properties / to / description

Previous value: -"The target article's id."New value: +"The target article, named the same ways."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "found": {
+      "type": "boolean"
+    },
+    "from": {
+      "type": "string"
+    },
+    "hops": {
+      "type": "integer"
+    },
+    "path": {
+      "items": {
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "steps": {
+      "items": {
+        "properties": {
+          "anchor": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "from": {
+            "type": "string"
+          },
+          "sentence": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "to": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "text": {
+      "type": "string"
+    },
+    "to": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "from",
+    "to",
+    "found",
+    "text"
+  ],
+  "type": "object"
+}

AddedOct 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavior: a hard bound of at most 6 hops and the fact that each hop is returned with the sentence that justifies it, disclosing the shape of the search rather than just its existence.

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?

A single front-loaded sentence with the action and constraint stated before the input-sourcing clause. No filler, no redundancy with the title, and the flow constraint (6 hops) is not buried.

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 not required, and the description still summarizes it briefly. Combined with annotations and a fully documented schema, an agent has what it needs, though it never states what happens when no chain exists within 6 hops.

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 coverage is 100%, so the baseline is 3. The description goes beyond the schema by clarifying that both arguments are ids obtained from `search`, which tells the agent where to source valid values rather than guessing at titles or slugs.

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?

Specific verb+resource: 'Find the shortest chain of in-text links from one Edgepedia article to another' states exactly what the tool does. It differentiates itself from siblings by tying its input to `search`'s output ('pass two ids as search returns them'), so an agent can distinguish it from fetch/related/resolve/search without opening schemas.

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?

Gives clear context for use: call `search` first, then pass the returned ids. It implicitly positions the tool after search in a workflow, but offers no explicit exclusions (e.g., when to prefer `related` or `resolve` instead), so it falls short of a 5.

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

All Edgepedia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.