Skip to main content
Glama
Datris MCP Server

Datris MCP Server

list_milvus_collections

Lists all collections in a Milvus vector database so you can discover available collections before running vector searches.

Instructions

List all collections in the Milvus vector database. Use this to discover available collections before running search_milvus.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral load: "List" implies a non-mutating enumeration, but it never states read-only status, what happens on connection failure, or whether results are paginated or truncated. For a trivial zero-argument listing tool this is a modest gap rather than a blocking one.

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 no filler: what it does is front-loaded and the usage hint follows immediately. Every clause adds information.

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 discovery tool with no output schema, the description covers purpose and workflow placement adequately. Adding a brief note on the return shape (a list of collection names) or failure behavior would close the last gap.

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 there is no parameter meaning to convey; the schema baseline of 4 applies. The description correctly implies no filtering or scoping inputs are needed.

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?

The description gives a specific verb and resource ("List all collections in the Milvus vector database"), and naming Milvus implicitly separates it from the many sibling list_*_collections tools for Chroma, Qdrant, MongoDB, and pgvector. It stops short of explicitly stating that it covers only Milvus and not other stores, so a small disambiguation gap remains.

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 states a concrete use case — discovering collections before calling search_milvus — which gives the agent an actionable trigger and names the follow-up tool. There is no explicit when-not-to-use guidance (e.g., when the database is unreachable or when a collection name is already known).

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