Skip to main content
Glama
mongodb-js

MongoDB MCP Server

Official
by mongodb-js

find

Read-only

Retrieve documents from a MongoDB collection by applying a filter, sort, projection, and limit in a find query.

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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentsYesThe documents returned by the find query
appliedLimitsYesThe limits applied to the find query
queryResultsCountNoThe total number of documents returned by the find query
Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds no additional behavioral context beyond stating it runs a find query. It does not mention result limits, pagination, or query behavior, but annotations cover the crucial safety profile, so a score of 3 is appropriate.

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 sentence that is highly concise and front-loaded. Every word is necessary, and there is no extraneous information. It effectively communicates the tool's purpose without waste.

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?

Given the output schema exists and annotations cover safety, the description is mostly complete for a simple read tool. It could mention that results are limited by default (limit:10) or that it returns documents, but the core functionality is clear. The minimalism is acceptable here.

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?

Schema coverage is 100% with all parameters described. The description does not add extra meaning beyond what the schema already provides, so baseline score of 3 is correct.

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 runs a find query against a MongoDB collection, which is a specific verb+resource combination. It effectively distinguishes this tool from siblings like 'aggregate', 'count', and 'explain', as these perform different operations.

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. Although the schema has a note in responseBytesLimit suggesting using 'export' for full results, the description itself lacks any contextual advice about when to prefer find over aggregate, count, or other query tools.

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