Skip to main content
Glama
Datris MCP Server

Datris MCP Server

list_weaviate_classes

Lists all classes in a Weaviate vector database so you can discover available classes before running a vector search.

Instructions

List all classes in the Weaviate vector database. Use this to discover available classes before running search_weaviate.

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_weaviate_classes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It implies a safe enumeration but never states that it is read-only, whether results are paginated or truncated, whether an empty result is possible, or what the returned entries contain (class names only vs. metadata). For a zero-parameter listing call the risk is low, but the behavioral gaps are real.

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 short sentences, with the purpose front-loaded and the prerequisite/sequencing hint second. Nothing redundant is included and no sentence is wasted.

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 a trivial input schema, no annotations and no output schema, the definition covers what an agent needs to decide to call it. The one remaining gap is the shape of the return value (plain class-name list vs. objects), which matters because there is no output schema to document it.

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 no parameters, so the baseline applies and there is nothing for the description to disambiguate. It correctly adds no parameter prose, keeping the definition clean.

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 states a specific verb and resource (list classes) scoped to a named backend (Weaviate vector database), which lets an agent separate it from the many sibling list_*_collections tools for Chroma, Milvus, Qdrant, pgvector and others without opening a schema.

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?

It gives explicit sequencing guidance: call this to discover available classes before running search_weaviate. That names the concrete downstream alternative, but it offers no when-not guidance (e.g. what to do when the class name is already known) and does not mention other Weaviate tools beyond search.

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