Skip to main content
Glama

Metis · Librarian — Create Knowledge Database

create_knowledge_database

Register a custom knowledge database layer to organize PDFs by folder and index them for cited research answers. Add domain-specific collections to your Metis library.

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. 'cardiology-specialist', 'soil-ecology').
    name:        Human-readable name (e.g. 'Cardiology 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 Economics']).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "name": "<name>"
    },
    "name": "create_knowledge_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
slugYes
layerNo
foldersNo
descriptionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the two-step create-then-index behavior and the layer numbering convention (4+ for custom, 1–3 reserved for built-ins), which is genuine context. It says nothing about duplicate-slug handling, whether registration is idempotent, permissions, or what happens to existing databases — gaps that matter for a persistent registration operation.

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?

Front-loads a one-line purpose, then the next-step workflow, then a compact Args block with per-parameter examples. Every section serves a function; the only mild redundancy is the example-heavy formatting of the args list.

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?

For a 5-parameter creation tool with no annotations and an available output schema, the description covers purpose, next steps, and all parameters. Remaining omissions — duplicate/validation behavior and the default meaning of an unset folders list — are modest but would help an agent avoid a failed or redundant call.

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 description coverage is 0%, and the description compensates well: it documents all five parameters, including format constraints ('URL-safe identifier'), intent ('human-readable name', 'what this database covers'), the layer numbering rule, and a concrete folders example path. It stops short of explaining what folders=null defaults to or whether folder paths must already exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Register a new custom knowledge database layer', which clearly separates it from list_knowledge_databases and delete_knowledge_database among siblings. The distinction between custom (layer 4+) and built-in (1-3) databases is a useful scope marker, though the terminology 'layer' is not fully explained.

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?

Gives an explicit follow-up workflow: place PDFs in knowledge/library/<your-folder>/ and then call build_pdf_knowledge_db(database='<slug>') to index. This names the downstream sibling tool and the exact condition for using it. It does not cover when *not* to create a database (e.g. when an existing one should be reused or extended).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools