Skip to main content
Glama
Sign In
utn-mcp

utn-mcp

by nialvape
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

aula_calendar_add_event

Creates a private event in the virtual classroom calendar so you can track reminders for exams or deadlines, with timezone-aware start times.

Instructions

Agrega un evento personal al calendario del aula virtual, que solo ve el usuario: por ejemplo un recordatorio de un parcial o una entrega. El aula avisa según la configuración de notificaciones del usuario. La fecha va con zona horaria; en Argentina es -03:00.

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": {
      "nombre": "<nombre>",
      "inicio": "<inicio>"
    },
    "name": "aula_calendar_add_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
inicioYesFecha y hora en ISO 8601 con zona horaria. Ej: "2026-10-14T18:00:00-03:00".
nombreYesTítulo del evento. Ej: "Parcial de Física II".
descripcionNoDetalle, en texto plano. Ej: "Aula 312, unidades 1 a 4".
duracionMinutosNoDuración en minutos. Por defecto, sin duración. Ej: 120.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.3

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (which only declare the write/non-destructive/non-idempotent profile), the description discloses two real behavioral traits: the event's visibility is private to the user, and creating it triggers notifications according to the user's notification settings. It does not cover failure modes or whether duplicates are permitted.

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?

Three short sentences, front-loaded with the core action and visibility scope, followed by side-effect and format notes. Every sentence carries information; nothing is repeated verbatim across sentences.

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 4-parameter, non-destructive create tool with annotations and no output schema, the description covers purpose, visibility, notification side effect and date format. Minor gaps remain around return value and duplicate handling, but nothing needed to invoke it correctly is 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 the schema already carries titles, formats and examples for all four parameters. The description reinforces the timezone requirement and localizes the offset for Argentina (-03:00), which adds modest value but largely restates the 'inicio' schema description.

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 and resource ('Agrega un evento personal al calendario del aula virtual') and adds a scope qualifier ('que solo ve el usuario') that separates it from shared/public posting tools like the forum siblings. It never names a sibling, so differentiation is by resource type rather than explicit contrast.

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?

Concrete use cases are given ('un recordatorio de un parcial o una entrega'), which tells the agent the intended context. There is no when-not guidance or named alternative, so it stops short of full routing instruction.

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

Deploy Server

Other Tools