Skip to main content
Glama
Beever-AI

Beever Atlas

Official

read_wiki_section

Fetch a narrative section from a wiki page using channel, page slug, and section anchor. Returns prose content without loading the entire page, saving tokens.

Instructions

Fetch ONE narrative (prose) section of a wiki page without loading the whole page. Call it when you know the page slug and section anchor and want just that article slice, to save tokens.

Disambiguation: read_wiki_section returns PROSE sections (paragraphs + citations); read_wiki_module returns a STRUCTURED module payload (key_facts, decision_banner, etc.); read_wiki_page returns the whole page. Use find_facts for fact-text search across pages.

Prerequisites: a channel_id (list_channels), a page_slug (list_wiki_pages), and an anchor (from the page's narrative sections).

Returns (instant, read-only): {anchor, heading, paragraphs, citations, visual, page_slug, page_title, channel_id}page_title and channel_id are included so you can attribute the section without a second call. No side effects.

Error modes (returned as dicts): 'authentication_missing' (no principal); 'channel_access_denied' (token lacks access to channel_id); 'page_not_found' (no such slug); 'section_not_found' (page exists but lacks the anchor — the result lists available_anchors to retry with); 'narrative_not_available' (page has no narrative sections — includes has_modules and a suggestion to use read_wiki_page for module data); 'internal_error'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYesChannel id. Get it from list_channels (e.g. 'ch-eng'). Required.
page_slugYesSlug of the page hosting the section (e.g. 'auth-architecture'). Discover slugs via list_wiki_pages. Required.
anchorYesSection anchor — kebab-case in-page id of one narrative section (e.g. 'context', 'alternatives', 'implications'). If you don't know it, a 'section_not_found' error lists the available anchors. Required.
target_langNoBCP-47 language tag (e.g. 'en', 'fr'). Default 'en'.en

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, so description carries full burden. It declares it is 'instant, read-only' with 'no side effects'. Lists error modes and return fields comprehensively, providing full behavioral transparency.

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?

Well-structured with clear paragraphs: purpose, disambiguation, prerequisites, return signature, error modes. Every sentence adds value; no fluff.

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?

With 4 parameters (3 required), 100% schema coverage, and an output schema (return fields listed), the description covers all necessary context: prerequisites, error handling, return format, and usage guidance. Fully complete for the tool's complexity.

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%, but description adds context: anchor is 'kebab-case in-page id' and mentions error handling for unknown anchors; target_lang default noted. Provides extra guidance beyond the schema.

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 the verb 'Fetch ONE narrative (prose) section' and specifies the resource. It distinguishes from siblings read_wiki_module, read_wiki_page, and find_facts by explaining what each returns.

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?

Explicit when-to-use: 'when you know the page slug and section anchor and want just that article slice, to save tokens.' Includes disambiguation with siblings and prerequisites (channel_id, page_slug, anchor) with source tools listed in parentheses.

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