Edgepedia

Related Edgepedia articles

related

Read-onlyIdempotent

Find encyclopedia articles related to an Edgepedia article: its topic-mates, a few from each neighboring topic, and its geography neighbors. Pass its id, as for fetch. Returns groups of results; fetch a group's topic id for more.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`by`	No	"links" = articles cited together with it, and articles linking to what it links to.
`id`	Yes	An article's id, as `search` returns it (such as "mount-fuji").

Output Schema

TableJSON Schema

Name	Required	Description	Default
`by`	No
`id`	No
`geo`	No
`url`	No
`title`	No
`cocited`	No
`coupled`	No
`cousins`	No
`siblings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 7, 2026

addedOutput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "id",
+      "title",
+      "url",
+      "siblings",
+      "cousins",
+      "geo"
+    ]
+  },
+  {
+    "required": [
+      "id",
+      "title",
+      "url",
+      "by",
+      "cocited",
+      "coupled"
+    ]
+  }
+]

addedOutput schema / properties / by

Added value: +{
+  "enum": [
+    "links"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / cocited

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / coupled

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / required

Removed value: -[
-  "id",
-  "title",
-  "url",
-  "siblings",
-  "cousins",
-  "geo"
-]

AddedOct 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety bar is covered. The description adds real behavioral context beyond that: results come back grouped, and each group is a `topic` id that can be fetched for more.

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 tight sentences front-load the purpose, then the input convention, then the follow-up. The phrase 'a few from each neighboring topic' is slightly loose but informative rather than filler.

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 values need not be spelled out, and the description still adds the grouping and pagination-by-topic follow-up. Complete enough for a 2-param read tool with full schema coverage.

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%, so `id` and `by` are already documented in the schema. The description reinforces the `id` convention ('as for `fetch`') but says nothing about `by`, so it adds only marginal value over the structured fields – baseline 3.

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 encyclopedia articles related to an Edgepedia article') and it concretely decomposes 'related' into topic-mates, neighbors, and geography neighbors. It also names the sibling `fetch` for the id convention, so an agent can place it among the siblings 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?

Clearly implies the retrieval context and gives a concrete chaining rule ('fetch a group's `topic` id for more'), plus the 'id as for `fetch`' convention. It does not explicitly contrast with `connect` or `search`, so exclusions are absent.

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.