Skip to main content
Glama
Sign In
ravendb-mcp

ravendb-mcp

by johnib
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete-document

Delete a document from a RavenDB database by providing its unique document ID.

Instructions

Delete a document by ID

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": {
      "id": "<id>"
    },
    "name": "delete-document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ID of the document to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states that it deletes a document, which implies a destructive action. It does not mention whether the deletion is permanent, if any related data is affected, or what the response 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.

Conciseness5/5

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

The description is a single sentence with no wasted words. It is as concise as possible while conveying the core purpose.

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

Completeness3/5

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

For a simple delete tool with no output schema, the description gives the essential information (action and parameter). However, it lacks details on success/failure indicators, idempotency, or error conditions, which would be helpful for a complete context.

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 100% coverage (the one parameter 'id' is described). The description adds no additional meaning beyond the schema, as it simply repeats the concept of 'by ID'. Baseline score of 3 is appropriate.

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 clearly states the action (delete) and resource (document by ID). It is specific enough to distinguish from sibling tools like get-document or store-document, but does not elaborate on the scope or permanence of the deletion.

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, or any prerequisites or restrictions. It implies the tool should be used when you need to remove a document, but does not mention when not to use it (e.g., if you need to delete multiple documents).

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