Skip to main content
Glama
Datris MCP Server

Datris MCP Server

list_mongodb_databases

List all MongoDB databases available in the Datris platform to see what data has been ingested. Use it as the first step when exploring MongoDB destinations.

Instructions

List all MongoDB databases available in the Datris platform. Use this as the first step when exploring what data has been ingested into MongoDB destinations.

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

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?

No annotations are supplied, so the description bears full behavioral burden. A 'list' verb implies a safe read, and 'available in the Datris platform' hints at scope, but nothing is said about ordering, empty results when no databases exist, or whether access is filtered by permissions — gaps for a zero-annotation tool.

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 zero filler; the what (list MongoDB databases) is front-loaded and the when (first exploration step) follows immediately. Nothing is repeated from the name or title.

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 simple zero-param discovery tool with no output schema, the definition covers what it returns conceptually and where it fits in a workflow. It could note the return shape (list of database names) or behavior on an empty environment, but an agent has enough to invoke it correctly.

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 and the schema is an empty object, so there is nothing parameter-level to document and no compensation is needed. The description correctly does not invent arguments, keeping it consistent with 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+resource ('List all MongoDB databases') plus the scope qualifier 'available in the Datris platform.' The MongoDB qualifier implicitly separates it from list_postgres_databases and the various collection-listing siblings, though it never names an alternative explicitly.

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?

'Use this as the first step when exploring what data has been ingested into MongoDB destinations' gives a clear entry-point condition for a discovery workflow. It stops short of naming the natural follow-up (e.g. listing collections within a selected database), so the sequencing hint requires mild inference.

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