Skip to main content
Glama

[EXPERIMENTAL] Guardar Borrador de Tarea en EVA

eva_guardar_borrador_tarea
Destructive

Saves a file or inline text as an editable draft assignment submission in EVA, requiring user confirmation before uploading.

Instructions

[EXPERIMENTAL] Sube un archivo o texto a EVA en modo borrador editable. Requiere confirmación del usuario.

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": {
      "cmid": "<cmid>"
    },
    "name": "eva_guardar_borrador_tarea"
  }
}

Input Schema

NameRequiredDescriptionDefault
cmidYesID numérico de la tarea o módulo en EVA (cmid)
ruta_archivoNoRuta absoluta local del archivo a subir como borrador
texto_en_lineaNoTexto en línea para el borrador de entrega (máx 350 caracteres)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.0.8
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / cmid / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / cmid / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / cmid / minimum
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "aprobado": {
      -      "type": "boolean"
      -    },
      -    "detalles": {
      -      "additionalProperties": {},
      -      "type": "object"
      -    },
      -    "exito": {
      -      "type": "boolean"
      -    },
      -    "instruccion": {
      -      "type": "string"
      -    },
      -    "mensaje": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "exito",
      -    "mensaje"
      -  ],
      -  "type": "object"
      -}New value: +null
  2. First observedv1.0.6

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false; the description adds real value by clarifying that the write stays in an editable draft state and that user confirmation is required. It never says whether an existing draft is overwritten or what happens on success, which is exactly the context the destructive/non-idempotent hints make relevant.

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?

Two short sentences, front-loaded with the action and scope, nothing padded. The duplicated [EXPERIMENTAL] marker from the title is the only redundant token.

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 mutation tool with no output schema and destructive/non-idempotent hints, an agent cannot tell from the description what the call returns (draft ID? URL?), whether it overwrites a prior draft, or how to choose between file and inline text. Annotations cover the safety profile but the outcome semantics remain unaddressed.

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 100%, so all three parameters are documented in the schema with types and limits. The description only echoes "archivo o texto" and omits the important unwritten rule that ruta_archivo and texto_en_linea are alternative content sources (mutually exclusive, only cmid required), so it adds little beyond the schema.

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?

States a specific verb (subir/guardar) and resource (borrador de tarea en EVA) plus the two content channels (archivo o texto). It does not name a sibling to differentiate from (e.g. eva_responder_foro or a final submission tool), so it stops short of 5.

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?

"en modo borrador editable" implies the use case (save without submitting) and "Requiere confirmación del usuario" gives a precondition, but there is no explicit when-not or alternative named. The agent must infer the draft-vs-submit boundary.

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