Skip to main content
Glama

create_knowledge_database

Create a custom knowledge database to index PDFs from specified library folders and enable cited answers from your documents.

Instructions

Register a new custom knowledge database layer.

After creating, add PDFs to knowledge/library/<your-folder>/ and call
build_pdf_knowledge_db(database='<slug>') to index them.

Args:
    slug:        URL-safe identifier (e.g. 'dhis2-specialist', 'malaria-research').
    name:        Human-readable name (e.g. 'DHIS2 Specialist Knowledge').
    description: What this database covers.
    layer:       Layer number (4+ for custom; built-ins use 1–3).
    folders:     List of library subfolder paths to include
                 (e.g. ['open-access-books/Health Informatics & DHIS2']).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYes
nameYes
descriptionNo
layerNo
foldersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that custom databases use layer 4+ and built-ins use 1-3, and hints at the creation workflow. However, it does not mention potential errors (e.g., duplicate slug), permission requirements, or response behavior. Adequate but not thorough.

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 brief and well-structured: a one-sentence purpose, a workflow step, then a parameter list. Every sentence adds value without repetition. Front-loaded with the core function.

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 the tool has 5 parameters and an output schema, the description covers the core workflow and parameter meanings well. It lacks detail on edge cases (e.g., what happens if slug exists) and does not explain the output, but the output schema may cover that. Slightly incomplete but sufficient for typical use.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description provides clear explanations for all 5 parameters: slug (URL-safe with examples), name (human-readable), description (coverage), layer (constraint on value), folders (list example). This fully compensates for the missing schema descriptions.

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 registers a new custom knowledge database layer, using specific verb 'Register' and resource 'custom knowledge database layer'. This distinguishes it from sibling tools like build_pdf_knowledge_db (for indexing) and list_knowledge_databases (for listing).

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?

The description provides a clear workflow: after creation, add PDFs and call build_pdf_knowledge_db. It implies the order of operations but does not explicitly mention when not to use this tool or exclude alternatives, though the sibling context shows no direct alternatives for creation.

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/SVerITG/Metis'

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