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

zyta-sign-mcp

by blanck1945
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Listar firmas externas pendientes

kairo_list_external_requests

List open external signature requests for a specific document using ephemeral tokens.

Instructions

Lista los pedidos de firma externa (token efímero) abiertos para un documento.

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

Input Schema

NameRequiredDescriptionDefault
documentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states the basic listing action, omitting details like read-only nature, authentication needs, rate limits, or response format.

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

Conciseness4/5

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

The description is a single concise sentence with no extraneous words. However, it may be overly concise, missing important details a longer description could provide.

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

Completeness2/5

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

Given the absence of annotations, output schema, and parameter descriptions, the tool description is incomplete. It fails to inform the agent about return values, error conditions, or potential side effects.

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?

The single 'documentId' parameter has no schema description (0% coverage) and the tool description adds minimal meaning, only implying it identifies a document. The format or source of the ID is not explained.

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 clearly states the tool lists open external signature requests for a document, using a specific verb and resource. It distinguishes from sibling tools like kairo_request_external_sign or kairo_revoke_external_request, though it doesn't explicitly contrast with similar list functions.

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 on when to use this tool versus alternatives, nor any conditions or prerequisites. The description provides no context for appropriate usage scenarios.

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