Skip to main content
Glama

resumen_semanal

Summarizes upcoming and overdue assignments, open quizzes, recent announcements, and unread notifications in one call so students can quickly see pending work and new updates.

Instructions

Resumen de todo lo importante en una sola llamada: entregas próximas y vencidas, cuestionarios abiertos, anuncios recientes de profesores y notificaciones sin leer. Úsala para '¿qué tengo pendiente?' o '¿qué hay de nuevo?'.

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": "resumen_semanal"
  }
}

Input Schema

NameRequiredDescriptionDefault
diasNoDías hacia adelante para entregas

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the scope of what is aggregated and implies a read-only digest, which is the key behavioral fact for this tool. It omits whether results are truncated/paginated, any permission or enrollment requirement, and the shape of what comes back (counts vs full items).

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, zero filler: contents first, then the triggering use cases. Nothing is repeated and nothing needs to be trimmed.

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 one-parameter aggregation tool with no output schema, the description is complete enough about what the response covers, so an agent can decide to call it. The remaining gap is the absence of any note on result size/aggregation granularity or how the 'dias' window interacts with overdue items.

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% for the single 'dias' parameter (default 7, range 1-60, 'Días hacia adelante para entregas'), so the schema already does the work. The description never mentions the parameter, and notably does not reconcile the forward-looking window with 'vencidas' (overdue) items it claims to include.

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?

The description names a specific deliverable (an aggregated weekly summary) and enumerates its contents: upcoming and overdue assignments, open quizzes, recent teacher announcements, and unread notifications. That enumeration distinguishes it in substance from the granular siblings (anuncios, cuestionarios, notificaciones, proximos_vencimientos), though no sibling is named explicitly.

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

Usage Guidelines4/5

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

It supplies concrete triggering questions ('¿qué tengo pendiente?', '¿qué hay de nuevo?') and the phrase 'en una sola llamada' implicitly contrasts it with the individual per-resource tools. It stops short of explicitly saying to use the per-resource siblings when detail on a single category is needed.

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