Skip to main content
Glama
Datris MCP Server

Datris MCP Server

list_mongodb_collections

List MongoDB collections from a specified database or across all databases in db.collection format, so you can quickly inspect available data before querying or ingestion.

Instructions

List MongoDB collections. If database is specified, lists collections in that database. If omitted, lists all collections across all databases in 'db.collection' format.

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

Input Schema

NameRequiredDescriptionDefault
databaseNoDatabase name (optional; omit to list from all databases)

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 supplied, so the description carries the full disclosure burden. It does add genuinely useful behavior: the omitted-parameter fallback and the 'db.collection' output naming convention. It says nothing about permissions, result size, or pagination limits, which matters for an unscoped all-databases list.

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 tight sentences with the core purpose front-loaded and the branch condition immediately after. No filler or redundancy, though the last two sentences restate the same parameter behavior twice in slightly different words.

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 single optional parameter read-only list tool with no output schema, the description covers the one meaningful branch and explains the returned key format. Only the absence of volume or permission expectations keeps it from being fully complete.

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

Parameters3/5

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

Schema coverage is 100% and the schema description already states the parameter is optional and what omission does. The description restates that plus the output format, adding a little value but no new syntax, casing, or naming constraints beyond the schema.

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 ("List MongoDB collections") immediately, so the agent knows exactly what it returns. It does not explicitly distinguish itself from siblings like list_chroma_collections or query_mongodb, relying on the tool name for that separation.

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 gives clear conditional guidance: pass a database to scope the result, omit it to sweep all databases. It does not state when an alternative tool (e.g. query_mongodb) would be more appropriate, so it stops short of full when-not coverage.

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