Skip to main content
Glama
MCP Dokploy Online
by igoruam

mongo-search

Read-onlyIdempotent

Search MongoDB instances in Dokploy by query, name, app, project, environment, or description with pagination controls.

Instructions

GET /mongo.search

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": "mongo-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
nameNo
limitNo
offsetNo
appNameNo
projectIdNo
descriptionNo
environmentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered structurally. The description adds nothing on top of that: it does not say whether results are paginated beyond limit/offset, whether q is a free-text or query-language input, whether all filters are ANDed, or what the response looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is technically short, but its brevity comes from under-specification rather than economy — an endpoint path fragment is not a front-loaded explanation of purpose. There is no sentence an agent could act on beyond the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, zero-required, undocumented search endpoint with no output schema, this is completely inadequate. Neither filter semantics, result shape, nor pagination behavior is described, so an agent must guess at nearly every invocation decision.

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

Parameters1/5

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

Schema description coverage is 0% across 8 parameters, so the description carries the full burden and provides none of it. The ambiguity is severe: q versus name versus description versus appName/projectId/environmentId could each be a match filter or a scope constraint, and nothing in the text clarifies limit/offset interaction.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"GET /mongo.search" is essentially an HTTP method plus path that restates the tool name rather than describing what is searched. An agent learns only that this is a read-style search against Mongo, with no statement of what resources (instances, databases, collections, logs) are queried or how it differs from sibling searches like application-search or project-search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance whatsoever. There is no mention of when this tool is preferred over mongo-one, mongo-readLogs, or the other *-search siblings, and no prerequisites, exclusions, or fallback behavior are stated.

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