Edgepedia

Search Edgepedia

search

Read-onlyIdempotent

Search an encyclopedia for facts about a person, place, thing, event, or concept: Edgepedia, more than 500,000 articles with citations. Pass the subject's name ("Mount Fuji", "photosynthesis"), not a question; other names and misspellings match, and when no title matches, articles whose text does follow, marked match: fulltext. Returns results with id, title, url, and preview text, plus a topic: result when the query names a topic ("painters"); pass an id to fetch. limit and page reach further results.

Input Schema

Name	Required	Description
`page`	No	Which page of results, from 1.
`sort`	No	central = the most-linked subjects first.
`first`	No	true = only the best match.
`limit`	No	Results a page, 1 to 30 (default 10).
`query`	Yes	The name of a subject, or words from an article title.
`topic`	No	Only articles under this topic id (as `fetch` topic:… names it, without "topic:").

Output Schema

Name	Required	Description
`page`	No
`pages`	No	Pages of results at this limit; pass `page` for the next.
`results`	Yes
`did_you_mean`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 7, 2026

addedInput schema / properties / first

Added value: +{
+  "description": "true = only the best match.",
+  "type": "boolean"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Results a page, 1 to 30 (default 10).",
+  "maximum": 30,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / page

Added value: +{
+  "description": "Which page of results, from 1.",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / sort

Added value: +{
+  "description": "central = the most-linked subjects first.",
+  "enum": [
+    "relevance",
+    "central"
+  ],
+  "type": "string"
+}

addedInput schema / properties / topic

Added value: +{
+  "description": "Only articles under this topic id (as `fetch` topic:… names it, without \"topic:\").",
+  "type": "string"
+}

addedOutput schema / properties / page
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / pages

Added value: +{
+  "description": "Pages of results at this limit; pass `page` for the next.",
+  "type": "integer"
+}

addedOutput schema / properties / results / items / properties / canonical_id

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

Changed1 schema field changedOct 4, 2026

changedOutput schema / properties / results / items / properties / text / description

Previous value: -"The article's opening sentences, or for a topic its article count and place in the tree."New value: +"The corpus snippet when available, otherwise the article opening; for a topic its article count and place in the tree."

Changed2 schema fields changedSep 29, 2026

addedOutput schema / properties / results / items / properties / articles

Added value: +{
+  "description": "A topic only: the articles under it.",
+  "type": "integer"
+}

changedOutput schema / properties / results / items / properties / text / description

Previous value: -"The article's opening sentences."New value: +"The article's opening sentences, or for a topic its article count and place in the tree."

First observedSep 20, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the description's added value is in matching semantics: other names and misspellings match, and fulltext fallback results are flagged with `match: fulltext`. It also discloses that a `topic:` result may appear and that limit/page reach further results, though it does not describe ranking or result-count behavior beyond pagination.

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 the key query constraint are front-loaded, and every sentence carries information. The middle sentence is long and clause-heavy, packing matching behavior, return fields, topic results, and fetch handoff together, but it remains readable.

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 six parameters, full schema coverage, annotations, and an output schema, the description covers the important operational details: query shape, fuzzy/fulltext matching, pagination, topic results, and fetch handoff. The main remaining gap is the lack of guidance on choosing this tool versus the sibling resolve or related tools.

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 would be 3; the description earns more by clarifying that the query should be a subject name rather than a question and by explaining that limit and page traverse further results. The topic and sort parameters are left mostly to their schema descriptions, but the query guidance is meaningfully richer than the schema text.

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 opens with a specific verb and resource — searching an encyclopedia for facts about a person, place, thing, event, or concept — and names Edgepedia with its scale and citation coverage. An agent can immediately distinguish this from fetch, which is explicitly mentioned as the follow-up tool for a returned id.

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?

It gives clear query-shape guidance (pass a subject name such as "Mount Fuji" or "photosynthesis", not a question) and explains the handoff to fetch. It does not explain when to prefer search over the sibling tools resolve or related, so it stops short of explicit alternatives/exclusions.

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.