Skip to main content
Glama
Sign In
Cuéntica MCP

Cuéntica MCP

by dacmail
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_document

Destructive

Permanently remove a document from Cuéntica using its ID. This action cannot be undone, so confirm with the user before proceeding.

Instructions

⚠️ Elimina un documento (irreversible). Confirmar con usuario.

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

Input Schema

NameRequiredDescriptionDefault
document_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

While the destructiveHint annotation already flags the tool as destructive, the description adds the important context that the action is irreversible and requires user confirmation. This provides behavioral transparency beyond the annotation.

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 concise sentence with a warning emoji, front-loading the key information. Every word is meaningful and there is no redundancy.

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

Completeness4/5

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

For a simple one-parameter destructive tool, the description covers the essential behavior (deletion, irreversibility, need for confirmation). It does not mention the output schema, but per guidelines that is not required. Minor room for improvement: could note any side effects or dependents.

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?

The input schema has zero description coverage for the only parameter (document_id), and the description does not explain what document_id represents, how to obtain it, or any constraints. The description adds no semantic value for the parameter.

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

Purpose5/5

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

The description clearly states the action ('deletes a document') and the resource ('document'), distinguishing it from sibling tools like delete_customer or delete_invoice. The irreversibility is explicitly noted, leaving no ambiguity.

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

Usage Guidelines3/5

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

The description includes a usage guideline: 'Confirm with user', indicating this tool should not be used without user consent. However, it does not specify when to use it over alternatives (e.g., why not use another delete tool for a different entity) or provide exclusions.

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