zyta-sign-mcp

Eliminar estudio

kairo_delete_studio

Delete a study permanently using its unique identifier. Requires management role and write permissions.

Instructions

Elimina un estudio definitivamente. Requiere rol de 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": "kairo_delete_studio"
  }
}

Input Schema

Name	Required	Description	Default
`studioId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Jun 19, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations are provided, so the description carries full transparency burden. It discloses that deletion is permanent and requires specific role and scope, which is sufficient behavioral context for a destructive operation.

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?

Two sentences, minimal waste. The first sentence states the action, the second adds an important constraint. Perfectly front-loaded and concise.

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

Completeness4/5

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

For a simple delete tool with one parameter and no output schema, the description covers purpose, permanence, and access requirements. It could mention cascading effects (e.g., members, areas) but is complete enough for a single-param tool.

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 0% schema description coverage, the description should explain the 'studioId' parameter, but it does not. The parameter is implied by the tool's purpose, but the description adds no explicit semantics beyond the schema.

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 clearly states the verb 'Elimina' (delete) and the resource 'estudio' (studio), with 'definitivamente' (permanently) adding specificity. Among sibling tools like 'kairo_delete_studio_area', this uniquely targets the studio itself.

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

Usage Guidelines3/5

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

The description provides a prerequisite: 'Requiere rol de gestión y scope write', which guides access but does not specify when to use this tool over alternatives or indicate conditions to avoid using it.

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

Deploy Server