MongoDB
Tools to query and explore a MongoDB database
1.1.2MongoDB Toolkit
The MongoDB toolkit connects Arcade to a MongoDB instance, enabling agents to explore databases, discover collections, introspect schemas, and run queries or aggregations.
Capabilities
- Discovery: List all databases in a MongoDB instance and all collections within a database before any query is attempted.
- Schema introspection: Sample documents from a collection to infer field names and data types, compensating for MongoDB's schema-less nature.
- Document querying: Find documents with filter expressions, field projection, sorting, and MongoDB query operators (
$gte,$lte,$in,$regex, etc.). - Aggregation pipelines: Execute multi-stage pipelines (
$match,$group,$project,$sort,$limit,$lookup, and more) for complex data processing. - Document counting: Count documents in a collection matching an arbitrary filter without returning full documents.
Secrets
MONGODB_CONNECTION_STRING — The full MongoDB connection URI used to authenticate and connect to your MongoDB instance. It encodes the protocol, credentials, host(s), port, and database in a single string (e.g., mongodb+srv://username:password). Obtain it from wherever your MongoDB is hosted:
- MongoDB Atlas: Go to your cluster in the Atlas dashboard, click Connect → Drivers, choose your driver/version, and copy the connection string. Replace
<password>with the database user's password. - Self-hosted / on-prem: Construct the URI manually using the host, port, and credentials you configured in
mongodor your ops tooling. See the MongoDB connection string URI format docs for the full syntax and all supported options.
Ensure the database user referenced in the URI has at least read privileges on the target databases. For aggregations that use $lookup across collections, the user needs read access to all involved collections.
Store this value as an Arcade secret: https://docs.arcade.dev/en/guides/create-tools/tool-basics/create-tool-secrets. You can manage secrets at https://api.arcade.dev/dashboard/auth/secrets.
Available tools(6)
| Tool name | Description | Secrets | |
|---|---|---|---|
Execute a MongoDB aggregation pipeline on a collection.
ONLY use this tool if you have already loaded the schema of the collection you need to query.
Load the collection's schema first if it is not already known.
Returns a list of JSON strings, where each string represents a
result document from the aggregation
(tools cannot return complex types).
Aggregation pipelines allow for complex data processing including:
* $match - filter documents
* $group - group documents and perform calculations
* $project - reshape documents
* $sort - sort documents
* $limit - limit results
* $lookup - join with other collections
* And many more stages | 1 | ||
Count documents in a MongoDB collection matching the given filter. | 1 | ||
Discover all the collections in the MongoDB database.
Use when the list of collections is not known.
ALWAYS use this tool before any other tool that requires a collection name. | 1 | ||
Discover all the databases in the MongoDB instance. | 1 | ||
Find documents in a MongoDB collection.
ONLY use this tool if you have already loaded the schema of the collection you need to query.
Load the collection's schema first if it is not already known.
Returns a list of JSON strings, where each string represents a
document from the collection (tools cannot return complex types).
When running queries, follow these rules which will help avoid errors:
* Always specify projection to limit fields returned if you don't need all data.
* Always sort your results by the most relevant fields first. Use '_id' if you're unsure.
* Use appropriate MongoDB query operators for complex filtering ($gte, $lte, $in, $regex, etc.).
* Be mindful of case sensitivity when querying string fields.
* Use indexes when possible (typically on _id and commonly queried fields). | 1 | ||
Get the schema/structure of a MongoDB collection by sampling documents.
Since MongoDB is schema-less, this tool samples a configurable number of documents
to infer the schema structure and data types.
This tool should ALWAYS be used before executing any query.
All collections in the query must be discovered first by listing the database's collections. | 1 |