ravendb-mcp

query-documents

Execute RQL queries against RavenDB to retrieve and handle document results.

Instructions

Execute RQL queries with results handling

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

Input Schema

Name	Required	Description	Default
`query`	Yes	The RQL query to execute

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1May 25, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are present, so the description must fully disclose behavioral traits. It does not indicate whether the query is read-only or mutating, what side effects occur, or any security/rate-limit implications. 'Results handling' implies some processing but is unspecified, leaving a significant gap.

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?

The description is a single sentence, very concise and front-loaded. However, it sacrifices clarity for brevity; while efficient, it could benefit from a few more words to improve understanding without becoming verbose.

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 presence of sibling tools like 'initialize-connection' and 'select-database', the description omits critical context such as dependencies, return value format, or error behavior. With no output schema, the agent is left uninformed about what 'results handling' produces, making it incomplete.

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?

The input schema has one parameter 'query' with a description 'The RQL query to execute'. Since schema coverage is 100%, the description adds no additional meaning beyond what the schema already provides, resulting in an average score per guidelines.

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?

The description 'Execute RQL queries with results handling' names the specific language RQL but 'results handling' is vague and does not differentiate from get-document (which also returns results) or other query-like operations. It lacks a clear scope of what 'handling' entails, making it only somewhat distinct.

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 is provided on when to use this tool versus siblings like 'select-database' or 'get-document'. It does not state prerequisites (e.g., connection initialization) or conditions under which it should be preferred, forcing the agent to guess context.

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

Deploy Server