Skip to main content
Glama
mongo-readonly-mcp

mongo-readonly-mcp

by tboon0

mongo_count

Read-only

Count matching documents in a specified MongoDB profile and collection using an optional query filter. Use it to verify result volumes without modifying data.

Instructions

Count matching documents in a profile's collection.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
profileYes
collectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 counting is scoped to a profile's collection; it says nothing about cost on large collections, error behavior for unknown profiles, or what a "matching" document means without a filter.

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 or redundancy. Brevity here reflects under-specification rather than tight editing, but nothing is wasted.

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?

The tool is simple, but with 0% parameter coverage and no output schema, the description should explain the filter semantics and confirm the return value is a numeric count. Those omissions leave real gaps for correct invocation.

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 must compensate, and it only loosely does: "profile's collection" gestures at profile and collection, and "matching" hints at the query parameter. It never explains the query filter syntax (e.g., MongoDB query document), that query defaults to empty (count all), or the expected format of profile/collection identifiers.

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?

"Count matching documents in a profile's collection" gives a specific verb (count) and resource (documents within a named profile/collection), which clearly separates it from siblings like mongo_find or mongo_aggregate. It stops short of explicitly naming any alternative, so differentiation is inferred rather than stated.

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 prefer a count over mongo_find or mongo_aggregate, no mention that results can be narrowed with a filter, and no exclusions. The agent must guess the intended use from the name alone.

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