Skip to main content
Glama
mongo-readonly-mcp

mongo-readonly-mcp

by tboon0

mongo_list_collections

Read-only

List all collection names in a MongoDB profile's database to explore available data structures before running read-only queries.

Instructions

List collection names in a profile's database.

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": {
      "profile": "<profile>"
    },
    "name": "mongo_list_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 without the description's help. The description adds only the scoping detail that listing is confined to a single profile's database; it says nothing about whether system collections are included, ordering, or result size, which is modest added value above the annotations.

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 no filler; the resource and scope come first. It is efficient, though it is terse enough that the omission is under-specification rather than a structure problem.

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

Completeness3/5

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

For a one-parameter read-only listing tool, the description covers the essentials and the annotations carry the safety profile, so no output schema is needed. However, an agent still lacks guidance on the return shape (names only) and on the meaning of a profile identifier, leaving a real gap for even this simple tool.

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?

With one parameter at 0% schema description coverage, the schema only says 'profile' is a non-empty string. The phrase "a profile's database" does clarify that the parameter selects which database to enumerate, so the description compensates partially, but it never explains what a profile is or where to obtain its identifier.

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 and resource ('List collection names') plus its scope ('in a profile's database'), which clearly distinguishes it from mongo_list_profiles (profiles, not collections) and from document-level siblings like mongo_find. It stops short of naming a sibling to contrast with, so it lands at 4 rather than 5.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. Usage is only implied by the wording: an agent can infer this is a discovery step before mongo_find or mongo_aggregate, but must make that inference itself.

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