Skip to main content
Glama
mongodb-js

MongoDB MCP Server

Official
by mongodb-js

find

Read-only

Query a MongoDB collection to retrieve matching documents using filter, projection, sort, and limit options.

Instructions

Run a find query against a MongoDB collection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoA document, describing the sort order, matching the syntax of the sort argument of cursor.sort(). The keys of the object are the fields to sort on, while the values are the sort directions (1 for ascending, -1 for descending).
limitNoThe maximum number of documents to return
filterNoThe query filter, matching the syntax of the query argument of db.collection.find()
databaseYesDatabase name
collectionYesCollection name
projectionNoThe projection, matching the syntax of the projection argument of db.collection.find()
responseBytesLimitNoThe maximum number of bytes to return in the response. This value is capped by the server's configured maxBytesPerQuery and cannot be exceeded. Note to LLM: If the entire query result is required, use the "export" tool instead of increasing this limit.
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds minimal behavioral information beyond the annotations (readOnlyHint, destructiveHint) and the schema. It does not mention that the tool returns matching documents, how results are paginated, or query behavior details. However, it does not contradict annotations.

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

Conciseness5/5

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

The description is a single, clear sentence with no unnecessary words. It is front-loaded with the core action, making it efficient and easy to parse.

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?

Given the tool's complexity (7 parameters, nested objects, no output schema) and the presence of annotations, the description is adequate but minimal. It could have included notes on return behavior or performance, but it is sufficient for a basic understanding.

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?

All parameters are fully described in the input schema (100% coverage), so the description does not need to add parameter details. It provides no extra semantic context beyond the schema, justifying a baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's action ('Run a find query') and resource ('MongoDB collection'), leaving no ambiguity. It effectively distinguishes from siblings like 'count' or 'aggregate' by specifying the query type.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'aggregate', 'export', or 'count'. It lacks any context about preferred scenarios, prerequisites, or limitations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mongodb-js/mongodb-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server