Skip to main content
Glama

Inscripción a Examen Final en Guaraní

guarani_inscribir_examen
Destructive

Registers for a final exam in SIU Guaraní via a two-phase cycle with explicit user confirmation, using career, course, and exam call ID.

Instructions

Inscribe a examen final en SIU Guaraní mediante ciclo en dos fases y 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": {
      "carrera": "<carrera>",
      "materia": "<materia>",
      "llamado_id": "<llamado_id>"
    },
    "name": "guarani_inscribir_examen"
  }
}

Input Schema

NameRequiredDescriptionDefault
carreraYesNombre o código de la carrera
materiaYesNombre de la materia
llamado_idYesID del turno/llamado obtenido previamente de 'guarani_mesas_disponibles'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • removedInput schema / properties / llamado_id / pattern
      Removed value: -"^[a-zA-Z0-9_\\-\\.]+$"
  2. Changed3 schema fields changedv1.0.8
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "aprobado": {
      -      "type": "boolean"
      -    },
      -    "comprobante": {
      -      "type": "string"
      -    },
      -    "detalles": {
      -      "additionalProperties": {},
      -      "type": "object"
      -    },
      -    "exito": {
      -      "type": "boolean"
      -    },
      -    "instruccion": {
      -      "type": "string"
      -    },
      -    "mensaje": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "exito",
      -    "mensaje"
      -  ],
      -  "type": "object"
      -}New value: +null
  3. First observedv1.0.6

TDQS

B3.2/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 openWorldHint=false, so the safety profile is known. The description adds genuine value by disclosing that the call runs a two-phase cycle with user confirmation, but it never explains what each phase does, whether a confirmation token must be passed, or whether an existing inscription can be overwritten.

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?

A single sentence with the action and target front-loaded and no filler. It is efficient, though the unexplained 'ciclo en dos fases' clause costs it a point since it raises a question the description never answers.

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

Completeness3/5

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

For a destructive, non-idempotent mutation with no output schema, the description should explain what the two phases are and what the tool returns after the first one. Mentioning the two-phase flow and confirmation is a useful start, but the mechanics an agent needs to invoke it correctly are missing.

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 description coverage is 100%, so all three parameters are already documented, including where llamado_id comes from. The description adds nothing about parameter meaning, so it sits at the baseline for schema-complete inputs.

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 concrete verb plus resource ('Inscribe a examen final en SIU Guaraní'), which separates it from read-only siblings like guarani_mis_inscripciones_examen and guarani_mesas_disponibles. It doesn't explicitly name those siblings as alternatives, and the trailing 'ciclo en dos fases' phrase is opaque rather than clarifying.

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 statement of when to use this versus the listing tools, and no explicit prerequisites in the description itself (the dependency on guarani_mesas_disponibles for llamado_id lives only in the schema). The mention of user confirmation is behavioral, not routing guidance.

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