zyta-sign-mcp

Crear paquete de firma externa

kairo_create_external_bundle

Combine 2 to 25 PDFs into a single link for external signature requests. Configure recipient details, invite message, and signature field placement on specified pages.

Instructions

Varios PDFs en un solo link. Mínimo 2 documentos.

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": {
      "documentIds": "<documentIds>"
    },
    "name": "kairo_create_external_bundle"
  }
}

Input Schema

Name	Required	Description
`documentIds`	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

C2.3/5.0

Behavior2/5

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

The description hints at creating a link with multiple PDFs but does not disclose behavioral traits such as whether it sends an email (despite a 'sendEmail' parameter), what happens to the documents, or any side effects. No annotations exist to fill the gap.

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 extremely concise (two short Spanish phrases) and front-loaded. However, it sacrifices necessary detail for conciseness, making it under-specified for a tool with 6 parameters.

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 tool's complexity (nested placement object, 6 parameters, no output schema), the description is woefully incomplete. It fails to explain what an external bundle is, how placement works, or what happens after creation, leaving the agent without sufficient context.

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?

With only 17% schema description coverage, the description should compensate but does not. It only reiterates the 'minItems: 2' constraint ('Mínimo 2 documentos'). Parameters like 'recipientName', 'inviteMessage', and the complex 'placement' object are unexplained.

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

Purpose3/5

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

The description 'Varios PDFs en un solo link' indicates bundling multiple PDFs into one link, which conveys the core purpose. However, it does not differentiate from other signing tools like 'kairo_request_external_sign' or specify what an 'external bundle' is exactly.

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?

No guidance is provided on when to use this tool versus alternatives such as 'kairo_request_external_sign' or 'kairo_create_sequential_sign'. There are no prerequisites, conditions, or exclusion criteria mentioned.

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

Deploy Server