Skip to main content
Glama
MCP Dokploy Online
by igoruam

mongo-one

Read-onlyIdempotent

Retrieve a single MongoDB service by its mongoId to inspect configuration and status details in Dokploy.

Instructions

GET /mongo.one

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mongoId": "<mongoId>"
    },
    "name": "mongo-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
mongoIdYes

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, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: no statement about what is returned, whether a missing id errors or returns empty, or what openWorld access means for this route.

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?

Brevity here is under-specification rather than conciseness: a single route fragment with no verb-resource phrasing, no front-loaded purpose, and no structure an agent can act on.

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 a tool with a required identifier parameter, no output schema, and no annotation coverage of return semantics, the description should explain what is fetched and how the id is interpreted. It does neither, leaving the definition effectively unusable without guessing.

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?

There is one required parameter, mongoId, with 0% schema description coverage, so the description carries the full burden of explaining it. It says nothing — not whether mongoId is a database id, a name, or an ObjectId string, nor its format constraints.

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.one" only restates the tool name as an HTTP route verb; the resource is never described in plain language (a MongoDB instance? a config record?). It implies a single-item retrieval by contrast with sibling mongo-search, but nothing in the text states that distinction, so an agent cannot confidently tell what is returned.

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, when-not-to-use, or alternative guidance is given. The only cue is the implicit GET verb, and siblings such as mongo-search or mongo-readLogs are never referenced.

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