Skip to main content
Glama

Metis · Librarian — List Knowledge Databases

list_knowledge_databases

Lists all registered knowledge databases in Metis, including built-in and custom layers, with document counts, chunk counts, and last build dates to help you select the right data source.

Instructions

List all knowledge databases (layers) registered in Metis.

Shows built-in databases (PH background, Epi methods) and any custom databases the user has created. Reports layer, document count, chunk count, and last build date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_knowledge_databases"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are present, so the description carries the full burden. It implicitly frames the tool as a read-only enumeration with no parameters, which is low risk, and it names the fields returned, but it never explicitly says it is side-effect free, has no pagination, or requires no auth.

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?

Three short sentences, front-loaded with the core action, zero wasted setup. The 'Shows built-in… and any custom…' sentence partially restates 'List all', and the return-field sentence overlaps the output schema, so it is not maximally tight.

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 zero-parameter list tool with an output schema and no annotations, the description covers what it lists and roughly what comes back, which is enough to call it correctly. It could add a note that layers can be toggled via set_knowledge_layer_enabled, but nothing essential is missing.

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?

The tool takes zero parameters, so the baseline is 4. The description's mention of document count, chunk count, and last build date refers to output fields rather than inputs, and since an output schema exists this is informational rather than necessary.

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?

Specific verb ('List') plus resource ('knowledge databases/layers') with a clarifying parenthetical tying 'databases' to the domain term 'layers'. It enumerates the scope (built-in PH/Epi vs. custom), which helps distinguish it from search_pdf_knowledge or build_pdf_knowledge_db, though it doesn't name those siblings explicitly.

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?

Usage is implied – you'd call this to discover what layers exist before searching or deleting one – but the description never states when to prefer it over search_pdf_knowledge, list_background_packs, or get_pdf_index_stats. No exclusions or prerequisites are given.

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