Skip to main content
Glama
Sign In
MongoDB MCP

MongoDB MCP

by vishnuweb-a
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_document

Retrieve a single document from a specified MongoDB collection using a query filter.

Instructions

Find a single document.

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": {
      "collection_name": "<collection_name>",
      "query": "<query>"
    },
    "name": "find_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
collection_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It only states that it finds a single document, but does not explain what happens if multiple documents match, if none match, or what the return structure looks like.

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?

The description is a single concise sentence, making it easy to parse. However, it is overly terse and omits essential context, so it is under-specified rather than appropriately concise.

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?

Given the tool has 2 parameters, a nested query object, and no output schema, the description provides insufficient context for an agent to know how to invoke it correctly. It lacks parameter formats, return behavior, and usage examples.

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

Parameters1/5

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

The schema has two parameters with no descriptions, and the description does not explain what query or collection_name mean or how they interact. With 0% schema coverage, the description should compensate, but it remains silent on parameter semantics.

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?

The description uses the verb 'find' and identifies the resource as a single document, clearly indicating a retrieval operation. It distinguishes itself from collection-level tools by specifying 'single', but it does not explicitly differentiate from fetch_collection_data or explain the query parameter's role.

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 like fetch_collection_data or count_documents. There is no mention of conditions, prerequisites, or exclusions.

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

Deploy Server

Other Tools