Skip to main content
Glama
Sign In
zyta-sign-mcp

zyta-sign-mcp

by blanck1945
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Eliminar documento

kairo_delete_document

Permanently delete an uploaded document and all its associated signatures. Requires write access.

Instructions

Elimina un documento que subiste (y sus firmas asociadas). Requiere scope 'write'.

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": {
      "documentId": "<documentId>"
    },
    "name": "kairo_delete_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

Without annotations, the description carries full burden. It discloses that signatures are also deleted, which is important. However, it omits details like irreversibility, rate limits, or side effects, leaving some behavioral gaps.

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 extremely concise with two sentences. The first sentence conveys the core action and side effect, while the second adds the scope requirement. No unnecessary words.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the main action and scope. However, the lack of parameter explanation and response details leaves the agent somewhat underinformed.

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 schema has 0% coverage, and the description provides no information about the 'documentId' parameter, such as its format, source, or examples. This leaves the agent without guidance on what value to provide.

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 uses a clear verb ('Elimina') and resource ('documento'), and specifies that it deletes associated signatures. It distinguishes from sibling delete tools by indicating it applies only to documents the user uploaded.

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

Usage Guidelines4/5

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

The description states the required 'write' scope, which is a prerequisite. It also implicitly restricts usage to self-uploaded documents via 'que subiste', providing context but not explicit alternatives.

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