Skip to main content
Glama
Beever-AI

Beever Atlas

Official

read_wiki_module

Fetch a specific structured module from a wiki page by its anchor, avoiding full page load. Get targeted data such as key facts or decision banners.

Instructions

Fetch ONE structured module from a wiki page without downloading the whole page. Call it when you already know the page slug and the module anchor you want, and reading the full page via read_wiki_page would waste tokens.

When to use: you need just one module's structured data (e.g. the key_facts items, or a decision_banner's rationale + alternatives). When NOT to use: you need a narrative prose section (use read_wiki_section) or the whole page (use read_wiki_page). To learn a page's module anchors, read it once with read_wiki_page first.

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

Returns (instant, read-only): {channel_id, page_slug, anchor, module_id, data} where data is the module's structured payload. 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); 'module_not_found' (page exists but has no module with that anchor); 'wiki_module_read_failed' (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 module (e.g. 'auth-architecture'). Discover slugs via list_wiki_pages. Required.
anchorYesModule anchor — the stable in-page id of one structured module (e.g. 'key-facts', 'decision-banner', 'tension-callout'). Discover the available anchors by reading the page once with read_wiki_page. 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 explicitly states 'Returns (instant, read-only): ... No side effects.' and lists all error modes in detail. No contradictions.

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?

The description is well-organized with clear sections (summary, when to use/not, prerequisites, returns, error modes). It is concise and front-loaded with the key purpose.

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 4 parameters (3 required), 100% schema coverage, and output schema described, the description covers all necessary aspects including error modes. No gaps.

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 description coverage is 100%, baseline 3. The description adds context beyond schema by explaining how to obtain parameters (e.g., 'Get it from list_channels', 'Discover slugs via list_wiki_pages') and the purpose of 'anchor'.

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 explicitly states 'Fetch ONE structured module from a wiki page without downloading the whole page.' This is a specific verb (fetch) and resource (structured module), and it distinguishes from sibling tools like read_wiki_page and read_wiki_section.

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?

The description provides clear when-to-use and when-not-to-use guidance, including alternatives (read_wiki_section, read_wiki_page). It also lists prerequisites and how to discover parameters (channel_id, page_slug, anchor).

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