Edgepedia

Fetch an Edgepedia article

fetch

Read-onlyIdempotent

Read an encyclopedia article in full: one Edgepedia article as Markdown with its citations, by a search result's id. Returns id, title, text, url, and metadata (topic path, license, credit). A topic: id lists that topic's parent, narrower topics, and articles, 120 a page; topic:root is the top of the tree, topic:geo the geography tree. citations: false gives [n] markers instead of inline source links. Show the credit line with any text you quote.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	The id of a search result (the last part of the article's address, such as "mount-fuji", or a topic's "topic:…" id).
`ids`	No	More ids to fetch with `id` in one call, up to 10 in all.
`cite`	No	Add a reference in this format (csl, bibtex, ris, apa, mla, chicago, harvard).
`page`	No	A topic only: which page of its articles, from 1.
`links`	No	Add the articles linking here (in), the links it makes (out), or both.
`query`	No	Only the 3 passages that best match these words, each with a `cite_url`.
`quote`	No	A sentence from the article, or a chunk id: adds a `cite_url` that opens the page at it.
`chunks`	No	true = the text as paragraphs with stable ids, in `chunks`.
`cursor`	No	Where to continue, from a cut text's `next_cursor`.
`format`	No	The text as plain text, HTML, JSON-LD, or Turtle instead of Markdown.
`length`	No	snippet or lead for a short text; full (default) for the whole article.
`tables`	No	true = add the article's tables as JSON and CSV.
`outline`	No	true = add the list of the article's headings.
`section`	No	Only this section, by its heading ("Etymology", "History").
`citations`	No	Default true. false = [n] markers instead of inline source links; the numbered reference list stays.
`links_page`	No	With links "in" or "both": which 30 articles linking here, from 1.
`max_tokens`	No	Cut the text at a section boundary to about this many tokens; pass `next_cursor` as `cursor` for the rest.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No
`url`	No
`text`	No
`title`	No
`results`	No	With `ids`: one entry per id, in order: that fetch's answer, or { id, error: { code, message } }.
`metadata`	No
`moved_from`	No	The id asked for, when the article has since moved; store `id` or `canonical_id` instead.
`canonical_id`	No	The article's permanent id (ep…); `fetch` takes it, and it outlives an address change.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 7, 2026

addedInput schema / properties / links_page

Added value: +{
+  "description": "With links \"in\" or \"both\": which 30 articles linking here, from 1.",
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "id",
+      "title",
+      "text",
+      "url"
+    ]
+  },
+  {
+    "required": [
+      "results"
+    ]
+  }
+]

addedOutput schema / properties / results

Added value: +{
+  "description": "With `ids`: one entry per id, in order: that fetch's answer, or { id, error: { code, message } }.",
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / required

Removed value: -[
-  "id",
-  "title",
-  "text",
-  "url"
-]

Changed16 schema fields changedOct 7, 2026

addedInput schema / properties / chunks

Added value: +{
+  "description": "true = the text as paragraphs with stable ids, in `chunks`.",
+  "type": "boolean"
+}

addedInput schema / properties / cite

Added value: +{
+  "description": "Add a reference in this format (csl, bibtex, ris, apa, mla, chicago, harvard).",
+  "enum": [
+    "csl",
+    "bibtex",
+    "ris",
+    "apa",
+    "mla",
+    "chicago",
+    "harvard"
+  ],
+  "type": "string"
+}

addedInput schema / properties / cursor

Added value: +{
+  "description": "Where to continue, from a cut text's `next_cursor`.",
+  "type": "string"
+}

addedInput schema / properties / format

Added value: +{
+  "description": "The text as plain text, HTML, JSON-LD, or Turtle instead of Markdown.",
+  "enum": [
+    "text",
+    "html",
+    "jsonld",
+    "turtle"
+  ],
+  "type": "string"
+}

addedInput schema / properties / ids

Added value: +{
+  "description": "More ids to fetch with `id` in one call, up to 10 in all.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / length

Added value: +{
+  "description": "snippet or lead for a short text; full (default) for the whole article.",
+  "enum": [
+    "snippet",
+    "lead",
+    "full"
+  ],
+  "type": "string"
+}

addedInput schema / properties / links

Added value: +{
+  "description": "Add the articles linking here (in), the links it makes (out), or both.",
+  "enum": [
+    "in",
+    "out",
+    "both"
+  ],
+  "type": "string"
+}

addedInput schema / properties / max_tokens

Added value: +{
+  "description": "Cut the text at a section boundary to about this many tokens; pass `next_cursor` as `cursor` for the rest.",
+  "type": "integer"
+}

addedInput schema / properties / outline

Added value: +{
+  "description": "true = add the list of the article's headings.",
+  "type": "boolean"
+}

addedInput schema / properties / page

Added value: +{
+  "description": "A topic only: which page of its articles, from 1.",
+  "type": "integer"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "Only the 3 passages that best match these words, each with a `cite_url`.",
+  "type": "string"
+}

addedInput schema / properties / quote

Added value: +{
+  "description": "A sentence from the article, or a chunk id: adds a `cite_url` that opens the page at it.",
+  "type": "string"
+}

addedInput schema / properties / section

Added value: +{
+  "description": "Only this section, by its heading (\"Etymology\", \"History\").",
+  "type": "string"
+}

addedInput schema / properties / tables

Added value: +{
+  "description": "true = add the article's tables as JSON and CSV.",
+  "type": "boolean"
+}

addedOutput schema / properties / canonical_id

Added value: +{
+  "description": "The article's permanent id (ep…); `fetch` takes it, and it outlives an address change.",
+  "type": "string"
+}

addedOutput schema / properties / moved_from

Added value: +{
+  "description": "The id asked for, when the article has since moved; store `id` or `canonical_id` instead.",
+  "type": "string"
+}

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / id / description

Previous value: -"The id of a search result (the last part of the article's address, such as \"mount-fuji\")."New value: +"The id of a search result (the last part of the article's address, such as \"mount-fuji\", or a topic's \"topic:…\" id)."

First observedSep 20, 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, so the safety profile is covered; the description goes further by disclosing the return shape, that topic ids page 120 at a time, how `citations: false` changes output, and the licensing obligation to show the `credit` line. It stops short of discussing truncation/cursor behavior, which lives only in the schema.

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?

Purpose and return fields are front-loaded, then progressively more specialized behaviors. Dense and largely earned, though the middle sentences pile several distinct features (topic paging, citations, credit) into a run that could be split.

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?

With 17 params at full schema coverage and an output schema, the description needn't enumerate returns, yet it does enough to orient the agent (Markdown body, citations, topic listing). It omits explicit when-to-use guidance relative to the four siblings, which is the remaining gap.

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, but the description adds real meaning: the `topic:` id convention with concrete examples (`topic:root`, `topic:geo`), the 120-per-page default, and the behavioral contract of `citations: false`. These go beyond the terse schema strings.

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 specific verb (read), resource (an Edgepedia article), scope (in full, as Markdown with citations) and ties the input to a sibling ('by a `search` result's id'). An agent can tell this apart from search/related/resolve without opening the schema.

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?

It implies the workflow (get an id from `search`, then fetch it) and explains topic: ids and the citations flag, but never states when to prefer this over siblings like `related` or `resolve`, nor any exclusions. Usage is implied rather than prescribed.

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.