Skip to main content
Glama
mongo-readonly-mcp

mongo-readonly-mcp

by tboon0

mongo_list_profiles

Read-only

Lists named MongoDB connection profiles with host, port, and database details, helping you identify available connections without exposing credentials.

Instructions

List named MongoDB connections with host, port, and database; no credentials.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds a genuinely useful security note ("no credentials"), confirming secrets are not exposed, but says nothing about ordering, completeness of the list, or whether profiles are user-scoped.

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?

A single front-loaded sentence with zero filler, and the returned fields are listed compactly. The trailing "no credentials" phrase is slightly ambiguous between "needs no credentials" and "returns no credentials," which costs a point.

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?

With no output schema, the description usefully names the three returned fields, and the annotations already cover safety and openness. It is nearly complete for a zero-parameter listing tool; the only gap is whether the listed connection names are directly reusable as identifiers in sibling tools.

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 has zero parameters and 100% schema coverage, so the baseline is 4. The description correctly adds no parameter commentary, since there is nothing to clarify.

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?

The description gives a specific verb plus resource ("List named MongoDB connections") and names the returned fields (host, port, database). That is enough to separate it from siblings like mongo_list_collections or mongo_find, which operate on data rather than configured connections, though it never explicitly contrasts itself with them.

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?

No explicit when-to-use or when-not-to-use guidance is given, and no alternatives are named. Usage is only implied: the tool takes no parameters and returns connection names, so an agent can infer it is a discovery step before calling data tools, but the description never says so.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.