zyta-sign-mcp

Pedir firma externa (legacy)

kairo_request_external_sign

Creates a shareable external signing link for a recipient to sign a document, with configurable signature field placement on the PDF.

Instructions

Preferí kairo_get_sign_url(mode=external) o kairo_sign_workflow. Crea link externo con share links.

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_request_external_sign"
  }
}

Input Schema

Name	Required	Description
`documentId`	Yes
`recipientName`	No
`recipientEmail`	No
`inviteMessage`	No
`sendEmail`	No
`placement`	No	Ubicación de campos en el PDF.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Jun 19, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description is the sole source for behavioral traits. It only states it creates a link, but does not disclose mutation side effects, permission requirements, or other important behaviors.

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

Conciseness3/5

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

The description is concise with two sentences. However, the first sentence primarily discourages use, and the second is vague. It could be more direct while still providing necessary info.

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 the complexity of 6 parameters (including a nested object), no output schema, and low per-parameter documentation, the description is severely incomplete. It barely explains what the tool does, let alone how to use it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17%, and the description does not explain any parameters except minimally referencing 'share links.' It fails to compensate for the low coverage.

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 states 'Crea link externo con share links,' clearly indicating the tool creates an external sign link. It also explicitly names preferred alternatives (kairo_get_sign_url, kairo_sign_workflow), distinguishing it from siblings.

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

Usage Guidelines5/5

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

The opening sentence 'Preferí kairo_get_sign_url(mode=external) o kairo_sign_workflow' provides explicit guidance to avoid this tool and use alternatives. This is strong context for when not to use it.

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

Deploy Server