Skip to main content
Glama
Beever-AI

Beever Atlas

Official
by Beever-AI
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

read_wiki_page

Retrieve a complete wiki page by slug, returning markdown body and structured payload. Use after listing pages to get the full page content.

Instructions

Read ONE full wiki page by its slug from the redesigned slug-keyed wiki. Call it after list_wiki_pages tells you which slug you want, to get a page's complete content and structured payload.

Disambiguation: this is the slug-keyed redesign surface (arbitrary topic/entity pages). For the seven LEGACY fixed pages (overview, faq, decisions, ...) use get_wiki_page(page_type). Typical sequence: list_wiki_pages -> read_wiki_page(slug). To save tokens when you need only a slice, use read_wiki_module (one module) or read_wiki_section (one narrative section) instead of the whole page.

Prerequisites: a channel_id from list_channels and a slug from list_wiki_pages.

Returns (instant, read-only): the full WikiPage document including content_md (markdown body), kind + kind_schema (structured payload agents can iterate without re-parsing markdown), cross_links (title->slug), cross_links_broken (linked titles with no page yet), pin_state, and last_updated. Hidden pages are excluded unless the token carries the read:hidden_pages scope. No side effects.

Error modes (returned as dicts): 'authentication_missing' (no principal); 'channel_access_denied' (token lacks access to channel_id); 'wiki_page_not_found' (no such slug, or it is hidden and the token lacks read:hidden_pages); 'wiki_read_failed' (internal error).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYesChannel id. Get it from list_channels (e.g. 'ch-eng'). Required.
slugYesPage slug — the stable identifier of the page (e.g. 'auth-architecture'). Discover valid slugs with list_wiki_pages. Required.
target_langNoBCP-47 language tag for the rendered page (e.g. 'en', 'fr'). Default 'en'.en

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

No annotations provided, but the description fully covers: read-only, no side effects, returns full WikiPage document with fields (content_md, kind, cross_links, etc.), excludes hidden pages unless scoped, and lists four error modes. Very transparent.

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?

Well-structured with clear sections: purpose, disambiguation, prerequisites, returns, error modes. Front-loaded with main action. Slightly lengthy but every sentence adds value.

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

Completeness5/5

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

Given output schema exists, description still provides key return fields, prerequisites, error modes, and ties with sibling tools. Covers all needed context for reliable invocation.

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% with clear descriptions, so baseline is 3. Description adds value by linking parameters to prerequisites (channel_id from list_channels, slug from list_wiki_pages) and specifying default for target_lang.

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 clearly states it reads a full wiki page by slug from the redesigned slug-keyed wiki. It distinguishes from siblings like get_wiki_page (legacy fixed pages) and read_wiki_module/section (partial reads).

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

Usage Guidelines5/5

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

Explicitly instructs to call after list_wiki_pages, before read_wiki_module/section if full page needed. Disambiguates from get_wiki_page and lists prerequisites (channel_id, slug).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Beever-AI/beever-atlas'

If you have feedback or need assistance with the MCP directory API, please join our Discord server