Skip to main content
Glama
Sign In
rocketmatter-mcp

rocketmatter-mcp

by RosenAdvertising
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_document

Deletes a specified document from RocketMatter by providing its document ID and path.

Instructions

[Not in LCS /v1] /v1 documents is read-only; delete is not exposed. Fails loudly.

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": {
      "path": "<path>",
      "doc_id": "<doc_id>"
    },
    "name": "delete_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
doc_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

D1.3/5.0
Behavior2/5

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

The description says 'Fails loudly', which discloses that the tool will error, but it does not explain why it exists or what the error looks like. Without annotations, more detail is needed.

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

Conciseness2/5

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

The description is very short but ineffective. It prioritizes brevity over clarity, omitting essential context and failing to serve its purpose.

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?

Given no annotations and a non-functional tool, the description should at least explain why the tool exists or direct the user to an alternative. It is completely inadequate.

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?

Schema description coverage is 0%. The description provides no information about the two required parameters (path and doc_id), leaving their meaning entirely to the schema's titles.

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

Purpose1/5

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

The description states that delete is not exposed and the documents endpoint is read-only, contradicting the tool name 'delete_document'. The purpose is misleading; the tool does not perform deletion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use the tool. The description implies it should not be used at all, but the tool exists in the list without any condition or alternative.

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