Skip to main content
Glama

akb_browse

Access all vault documents, tables, and files by specifying a browse root with adjustable tree depth, content type filters, and pagination. Use a canonical URI or vault/collection pair for navigation.

Instructions

Browse ALL vault content — documents, tables, and files — under a browse root. The browse root can be addressed two ways: pass a canonical uri (akb://V for vault root or akb://V/coll/X for a collection), or the legacy vault + optional collection pair. Use the URI form when drilling down from a previous response — every item carries a uri that can be pasted straight back in.

depth is tree-depth from the browse root, mirroring tree -L N: 0 = direct children only (no descent), N = descend N collection levels, -1 = entire subtree. Collection rows are always emitted as navigation aids regardless of depth.

Response is slim by default (no summary field) so large vaults (70+ collections) fit in the agent's context window. Returns {vault, path, items, total, returned, truncated?, hint?}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriNoCanonical browse target: `akb://{vault}` (vault root) or `akb://{vault}/coll/{path}` (collection-scoped). Takes precedence over `vault` + `collection` when both are given.
vaultNoVault name. Required unless `uri` is given.
collectionNoCollection path to use as the browse root (omit for vault root). Ignored when `uri` is given.
depthNoTree depth from the browse root. 0 = direct children only (no descent into any collection). N = descend N collection levels. -1 = unbounded (entire subtree). Collections themselves are always emitted regardless of depth.
content_typeNoFilter by content typeall
filterNoSubstring filter on item name/path (case-insensitive).
limitNoCap returned item count.
offsetNoSkip first N items (default 0).
include_summaryNoInclude the per-item summary field (default false, drops to keep payload small).
include_hashesNoInclude AKB-certified content_hash/hash_algorithm and resource version fields for documents/files.
include_archivedNoInclude archived documents. Default false — `status: archived` docs are hidden from browse.
Behavior5/5

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

With no annotations, the description fully discloses behavior: slim response by default, depth semantics mimicking tree -L N, collection rows always emitted, filtering options, and return structure. This exceeds typical transparency.

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 with front-loading of main purpose and clear subsections. Every sentence adds value, though it could be slightly more concise without losing clarity.

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?

Given 11 parameters with 100% schema coverage and no output schema, the description explains key behaviors (depth, addressing, response format). It lacks explicit pagination behavior details but covers most ground adequately.

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 baseline is 3. The description adds value by explaining the precedence of uri over vault/collection, depth semantics, and defaults for include_summary and include_archived. Minor extra context beyond 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 it browses vault content (documents, tables, files) under a browse root, with two addressing methods. It distinguishes from siblings like akb_search and akb_get by focusing on hierarchical browsing.

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

Usage Guidelines3/5

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

The description explains how to address the browse root and suggests using URI when drilling down from previous responses. However, it does not explicitly differentiate from sibling akb_drill_down nor provide when-not-to-use guidance.

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/dnotitia/akb'

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