Skip to main content
Glama

Resumen Semanal del Alumno

uca_resumen_semanal
Read-onlyIdempotent

Retrieves upcoming EVA tasks, course notices, attendance and enrollment data, today’s classes, and Guaraní final exam registrations in parallel to compile a weekly academic summary.

Instructions

Tool Compuesta: Trae en paralelo tareas próximas de EVA, avisos de cátedra, cursada/inasistencias, clases de hoy e inscripciones a finales de Guaraní.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "uca_resumen_semanal"
  }
}

Input Schema

NameRequiredDescriptionDefault
carreraNoNombre o código de la carrera (opcional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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": {
      -    "alertas": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "avisosRecientes": {
      -      "type": "array"
      -    },
      -    "estadoCursada": {
      -      "type": "array"
      -    },
      -    "fechaGeneracion": {
      -      "type": "string"
      -    },
      -    "novedades": {},
      -    "tareasProximas": {
      -      "type": "array"
      -    }
      -  },
      -  "required": [
      -    "fechaGeneracion",
      -    "alertas",
      -    "tareasProximas",
      -    "avisosRecientes",
      -    "estadoCursada"
      -  ],
      -  "type": "object"
      -}New value: +null
  2. 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 readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds that retrieval happens in parallel across multiple backends, which is genuinely useful context, but it says nothing about authentication/session prerequisites (the uca_iniciar_sesion sibling hints at a login requirement) or what happens when one source fails.

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 dense sentence with the source list front-loaded and no redundancy. The 'Tool Compuesta:' prefix is slightly meta but earns its place by signalling aggregation.

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 tool merging five data sources with no output schema, an agent still lacks the shape of the returned summary, whether sections are omitted or null when a source is empty, and the auth/session requirement. The source enumeration is complete, but the operational details are thin.

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?

Only one optional parameter and the schema documents it at 100% coverage ('Nombre o código de la carrera (opcional)'), so the baseline is 3. The description never mentions the carrera filter or what it scopes, adding no meaning 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 ('Trae en paralelo') and enumerates exactly which resources it aggregates from EVA and Guaraní (tareas próximas, avisos, cursada/inasistencias, clases de hoy, inscripciones a finales). The label 'Tool Compuesta' signals it is an aggregator over sibling tools, though it never names those siblings explicitly to draw the contrast.

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 explicit when-to-use / when-not guidance. The 'Semanal' framing and 'Compuesta' prefix imply it is a periodic aggregate instead of calling the individual sibling tools, but the agent must infer that; nothing says to prefer this over eva_entregas_proximas or guarani_estado_cursada, or when the granular tools are still needed.

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