zyta-sign-mcp

Crear área de estudio

kairo_create_studio_area

Create a new area within a studio to organize documents and signatures. Requires write scope and management permissions.

Instructions

Crea un área dentro de un estudio. Requiere gestión y 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": {
      "studioId": "<studioId>",
      "name": "<name>"
    },
    "name": "kairo_create_studio_area"
  }
}

Input Schema

Name	Required	Description	Default
`studioId`	Yes
`name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Jun 19, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the burden. It only notes the write scope requirement, but does not disclose side effects, idempotency, or errors. For a creation tool, this is insufficient.

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 brief (two sentences), but it could be more helpful without being verbose. It is front-loaded with the action but lacks depth.

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?

For a simple creation tool with no output schema, the description should at least imply return value or success behavior. It does not, leaving the agent without knowledge of what the result is.

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?

Schema coverage is 0% and the description adds no parameter information. With 2 required parameters (studioId, name), the description should explain their meaning or constraints, but it does not.

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 it creates an area within a studio, with the verb 'creates' and resource 'area within a study'. It is distinct from siblings like kairo_create_studio which creates a studio at a higher level.

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?

The description mentions a precondition (requires write scope) but provides no guidance on when to use this tool versus alternatives like kairo_update_studio_area or kairo_delete_studio_area. No exclusions or contextual hints are given.

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

Deploy Server