zyta-expedientes-mcp

by blanck1945

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

zyta_expedientes_tareas_delete

Remove a task from an Argentine judicial case using its case UUID and task ID.

Instructions

Elimina una tarea. DELETE …/tareas/:id

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": {
      "expedienteId": "<expedienteId>",
      "tareaId": "<tareaId>"
    },
    "name": "zyta_expedientes_tareas_delete"
  }
}

Input Schema

Name	Required	Description	Default
`tareaId`	Yes
`expedienteId`	Yes	UUID del expediente

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states the action, lacking details about consequences, permissions, or side effects of deletion.

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 short and front-loaded, but could include more context without becoming verbose.

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 no output schema and low complexity, the description still misses necessary behavioral and usage context for a delete operation.

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

Parameters3/5

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

Schema coverage is 50%, and the description hints that tareaId corresponds to the path parameter, but does not clarify expedienteId's role. Baseline maintained.

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 action ('Elimina una tarea') and includes the HTTP method and endpoint pattern, differentiating it from sibling create, list, and update tools.

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

Usage Guidelines1/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, nor on prerequisites or effects such as irreversibility.

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