Skip to main content
Glama

akb_put

Store a new document in a specified vault and collection. Returns a canonical URI for addressing the document, which is automatically chunked and indexed for semantic search.

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.
Behavior4/5

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

Since annotations are absent, the description carries full burden. It discloses important behaviors: the response returns a canonical URI, and the document is automatically chunked and indexed for semantic search. Lacks coverage of idempotency, overwrite behavior, or error cases, but the given details are valuable.

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 sentences, highly concise. First sentence states purpose, second adds key behavioral info and response usage. No filler.

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 and no output schema, the description covers creation intent, behavior (chunking, indexing), and response format (URI). Missing details like the file-content exclusivity hint, but that is in schema. Overall sufficient context for an AI agent to understand the tool's role.

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 coverage is 100% with descriptions, so baseline is 3. The description does not add meaning beyond the schema; it mentions the response URI and indexing but not parameter interactions. The 'file' vs 'content' constraint is documented in schema, not in description.

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?

Clear verb-resource pair: 'Store a new document'. Differentiates from siblings like akb_edit and akb_update by specifying 'new'. The description also hints at the tool's role in the lifecycle by mentioning the canonical URI for subsequent addressing.

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?

No explicit when-not-to-use or alternatives. The description implies creation use, but does not mention when to use akb_edit or akb_update instead. The URI guidance is helpful but not a full usage guideline.

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