Skip to main content
Glama
mongo-readonly-mcp

mongo-readonly-mcp

by tboon0

mongo_find_one

Read-only

Retrieves one matching document from a MongoDB collection in a read-only profile, with optional query, projection, and sort controls for targeted data inspection.

Instructions

Read one matching document from a profile.

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

Input Schema

NameRequiredDescriptionDefault
sortNo
queryNo
profileYes
collectionYes
projectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not say which single document wins when several match, whether a null/empty result is returned on no match, or what 'profile' means as a connection target.

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?

A single front-loaded sentence with no filler, which is structurally clean. However, the brevity is achieved by omitting necessary content rather than by tight editing, so the terseness cuts against usefulness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Five parameters with zero schema descriptions and no output schema, yet the description says nothing about result shape, no-match behavior, or selection ordering. For a lookup tool whose whole behavior hinges on which document is picked, this is materially incomplete.

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% across five parameters, so the description carries the full burden and largely fails. 'Matching' loosely implies the query param and 'profile' names a required param, but sort, projection, and collection are given no meaning at all — especially consequential for a find-one tool where sort determines the returned document.

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?

States a specific verb and scope: 'Read one matching document from a profile.' The word 'one' distinguishes it in spirit from mongo_find, but the description does not name any sibling or state the contrast explicitly, which keeps it at a clear-but-undifferentiated 4.

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?

No guidance on when to prefer this over mongo_find or mongo_aggregate, and no note on what happens when multiple documents match or when nothing matches. The agent must infer usage entirely from the name.

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