Skip to main content
Glama
Beever-AI

Beever Atlas

Official

get_wiki_graph

Map wiki page connections in a channel to visualize structure and plan cross-page traversal.

Instructions

Return the map of how a channel's WIKI PAGES link to one another, as a node/edge graph. Call it to understand the wiki's structure — which pages reference which — or to plan a traversal across related pages.

Disambiguation: this is the WIKI PAGE-LINK graph (nodes are wiki pages, edges are cross-links between them). For the KNOWLEDGE graph of entities and their relationships (people, systems, concepts), use search_relationships instead.

When to use: visualizing or navigating wiki page structure, or finding clusters of related pages. When NOT to use: reading a page's content (use read_wiki_page) or querying entity relationships (search_relationships).

Prerequisites: a channel_id from list_channels.

Returns (instant, read-only): Cytoscape-format {channel_id, nodes: [{data: {id, label, kind, page_kind?, version?, last_updated?}}], edges: [{data: {id, source, target, kind}}]}. Returns empty nodes/edges arrays (not an error) when the graph backend is unavailable, so it is always safe to call. No side effects.

Error modes (returned as dicts): 'authentication_missing' (no principal); 'channel_access_denied' (token lacks access to channel_id).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYesChannel id. Get it from list_channels (e.g. 'ch-eng'). Required.

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 the description fully carries the burden. It discloses the tool is instant, read-only, has no side effects, returns empty arrays when backend is unavailable (always safe), and lists specific error modes. This is comprehensive behavioral coverage.

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?

The description is well-structured into clear sections (purpose, disambiguation, usage, returns, error modes) and all sentences are informative. While slightly lengthy, it earns its length with valuable detail. A minor reduction could improve conciseness.

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 the tool's complexity (graph output) and lack of annotations, the description provides thorough context including output format (Cytoscape-format), behavior on unavailable backend, and error scenarios. Output schema exists, but the description still adds valuable detail about edge/node structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter (channel_id) with 100% schema description coverage. The description adds minor context (mentioning source list_channels) but does not significantly enhance understanding beyond the schema. Baseline 3 is appropriate.

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 tool returns a wiki page-link graph as a node/edge map. It distinguishes from the knowledge graph (use search_relationships) and other wiki tools like read_wiki_page. The verb 'return' and resource 'wiki page-link graph' are specific and unambiguous.

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 describes when to use the tool (visualizing/navigating wiki structure, finding clusters) and when not to (reading page content, querying entity relationships, with alternatives named). It also lists prerequisite channel_id from list_channels.

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