Skip to main content
Glama

akb_put

Store a new document in a knowledge base vault. Automatically chunked and indexed for semantic search, returns canonical URI for later access.

Instructions

Store a new document. The response carries the canonical uri (akb://{vault}/doc/{path}) — use that to address the document from every other tool. Automatically chunked and indexed for semantic search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vaultYesTarget vault name
collectionYesCollection (directory) path, e.g. 'api-specs' or 'meeting-notes'
titleYesDocument title
contentYesDocument body in Markdown
typeNoDocument typenote
tagsNoTags for classification
domainNoDomain: engineering, product, ops, legal, etc.
summaryNoBrief summary (auto-generated if omitted)
depends_onNoakb:// URIs this depends on
related_toNoakb:// URIs of related resources
fileNoLocal file path to read as document body (alternative to content). Provide either file or content, not both.
Behavior3/5

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

Discloses auto-chunking and indexing for semantic search, and that response carries canonical URI. No annotations provided, so description carries burden; lacks details on permissions, overwrite behavior, or error conditions.

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?

Two concise sentences front-loading the action. No wasted words.

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?

Explains key output (URI) and behavior (chunking/indexing). Lacks coverage of error handling or prerequisites, but sufficient for a create tool with comprehensive schema.

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?

Schema covers 100% of parameters with descriptions. Description does not add parameter-level detail; baseline score applies as schema does the heavy lifting.

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?

Description clearly states 'Store a new document' with a specific verb and resource. It distinguishes from sibling tools like akb_update (update) and akb_get (retrieve).

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

Usage Guidelines4/5

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

Implies use for new documents and mentions using the returned URI for other tools. Does not explicitly exclude use for updates or list alternatives, but context from sibling names provides differentiation.

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