Skip to main content
Glama
mongo-readonly-mcp

mongo-readonly-mcp

by tboon0

mongo_collection_stats

Read-only

Read collection statistics for a specified MongoDB profile and collection to inspect storage, document, and index metrics during read-only database analysis.

Instructions

Read collection statistics from a profile.

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>",
      "collection": "<collection>"
    },
    "name": "mongo_collection_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYes
collectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/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 only that stats are scoped to a profile, with no mention of which statistics are returned, permissions required, or whether stats are live or cached.

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

Conciseness3/5

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

A single front-loaded sentence with no wasted words, but its brevity reflects under-specification rather than deliberate economy. It is efficient but does not earn its place by conveying much.

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

Completeness2/5

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

With no output schema, no parameter descriptions, and a vague one-line description, an agent cannot predict the return shape (counts, sizes, indexes?) or the format of inputs. For a tool with two mandatory arguments, more context is needed.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden for both required parameters. It never clarifies whether 'profile' is a connection name or an ID, or whether 'collection' accepts namespaces, leaving both parameters name-inferred only.

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?

Uses a specific verb and resource ('Read collection statistics') scoped to a profile, which is enough for an agent to distinguish it from mongo_find, mongo_count, and mongo_aggregate. It stops short of explicitly contrasting itself with those siblings, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

There is no guidance on when to call this instead of mongo_count, mongo_list_collections, or mongo_aggregate, nor any stated prerequisites for choosing a profile. The agent must infer usage entirely from the tool name.

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