Skip to main content
Glama
mongo-readonly-mcp

mongo-readonly-mcp

by tboon0

mongo_find

Read-only

Query and retrieve documents from a MongoDB collection by named profile, using optional filters, projection, sort, skip, and limits up to 1000 for read-only inspection.

Instructions

Read documents from a profile. Default limit 100, maximum 1000.

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

Input Schema

NameRequiredDescriptionDefault
skipNo
sortNo
limitNo
queryNo
profileYes
collectionYes
projectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: a default result cap of 100 and a hard maximum of 1000, which tells the agent results are truncated and bounded. It says nothing, however, about pagination via skip, ordering guarantees, or whether truncated results are indicated.

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

Conciseness4/5

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

Two short sentences, front-loaded with the action and then the result-size constraint; no filler. Brevity here is real, though the space saved is space that parameter documentation needed.

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?

For a 7-parameter, open-world read tool with no output schema and no parameter descriptions, the definition is far too thin. An agent has no idea of the query dialect, what sort or projection accept, what a profile is, or how paging works, so correct invocation depends on guessing.

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 7 parameters, so the description carries the full explanatory burden and largely fails it. It only touches limit (default and maximum, both effectively in the schema); query, sort, projection, skip, profile and collection are entirely undefined in both places.

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

Purpose3/5

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

"Read documents from a profile" gives a verb and resource, and the plural "documents" hints at a multi-result read versus mongo_find_one. But it never names the siblings or states what distinguishes this from mongo_aggregate or mongo_find_one, and "profile" is left unexplained, so the purpose is only loosely pinned down.

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?

There is no when-to-use guidance at all: no condition that selects this over mongo_find_one for a single document, mongo_aggregate for computed results, or mongo_count for counting. The read-only framing only implies the category, not the choice.

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