Skip to main content
Glama
Sign In
MongoDB

MongoDB

by kiliczsh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

serverInfo

Fetch MongoDB server details including version, storage engine, and configuration. Optionally include debug information for deeper analysis.

Instructions

Get MongoDB server information including version, storage engine, and other details

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": "serverInfo"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeDebugInfoNoInclude additional debug information about the server

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries full burden. It correctly implies a read-only, non-destructive operation but does not disclose any specific behavioral traits such as authentication needs or rate limits. The effect of the optional parameter is not elaborated beyond the schema.

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?

The description is a single, efficient sentence that conveys the core purpose. It is front-loaded and concise, though it could be slightly more structured.

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 info tool with one optional parameter and no output schema, the description is mostly complete, stating the type of information returned. It lacks details about return format or explicit read-only guarantee, but is still adequate.

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 parameter already has a description. The tool description adds no additional meaning about the parameter beyond what the schema provides, so a baseline score of 3 is appropriate.

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 clearly states the tool gets MongoDB server information and lists examples like version and storage engine, distinguishing it from sibling tools that perform data operations (query, insert, etc.).

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?

The description gives a clear purpose but does not explicitly state when or when not to use this tool versus alternatives. Context from sibling tools suggests usage, but no direct guidance is provided.

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