Skip to main content
Glama

aula

Read-onlyIdempotent

Verifies a student's class schedule, room, and time for a date and cross-references teacher notices, course plans, assessments, and university calendars to flag cancellations, room changes, or exam days.

Instructions

Verifica bloco, sala e horário das aulas do estudante em uma data e cruza automaticamente com os avisos recentes do professor (com filtro temporal de relevância), o cronograma do Plano de Curso, avaliações agendadas e o Calendário Universitário para alertar se a aula foi cancelada, mudou de sala/laboratório ou se é dia de prova.

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

Input Schema

NameRequiredDescriptionDefault
dataNo
id_turmaNo
atualizarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. Beyond that, the description usefully discloses that it aggregates four separate sources and applies a temporal relevance filter to notices before emitting alerts - behavior an agent could not infer from the annotations.

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?

One dense sentence with the action verb front-loaded and each clause carrying information about a distinct data source. It is long but not padded, though the nested clause structure slightly slows parsing.

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?

An output schema exists, so return values need not be described, and the alert categories (cancelada, mudou de sala, dia de prova) are stated. However, for a tool with zero parameter documentation, it omits default behavior (e.g., whether data defaults to today) and the meaning of atualizar, leaving gaps an agent must guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and all three parameters (data, id_turma, atualizar) are undocumented. The description only hints at a date concept ('em uma data'); it never explains the date format, what id_turma selects, or what atualizar (refresh) does, so the schema gap is not compensated.

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 uses a specific verb (verifica/cruza) and enumerates distinctive resources: bloco, sala, horário, avisos do professor, Plano de Curso, avaliações and Calendário. The multi-source cross-referencing makes it clearly different from simpler siblings like horario or dia, though it never names those siblings to contrast with.

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?

Usage is only implied: an agent can infer it should call this when checking whether a class is happening or changed on a given date. There is no explicit when-not guidance, no mention of how it relates to siblings such as horario, dia or avisos, and no statement about what happens when no date is supplied.

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