Skip to main content
Glama

alertas

Read-onlyIdempotent

Flags academic risks by identifying courses near the absence limit, calculating grades needed to pass or take a final exam, and listing upcoming exams, task deadlines, and library pending items.

Instructions

Painel proativo de riscos acadêmicos do estudante: identifica disciplinas próximas do limite de 25% de faltas (Art. 113), calcula notas necessárias para aprovação ou Avaliação Final (Art. 114), classifica tarefas por prazo e situação de envio, e lista provas próximas e pendências na biblioteca.

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

Input Schema

NameRequiredDescriptionDefault
atualizarNo
dias_antecedenciaNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description usefully signals that outputs are derived/calculated (grade thresholds, classification), but it omits behavioral facts an agent needs: whether results are cached or fetched live, and what the refresh flag actually triggers. For a multi-source aggregation tool that extra context would be the real value-add.

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 that is front-loaded with the tool's identity and then enumerates its outputs in a scannable list. Efficient, though slightly long and packing four distinct behaviors without separation.

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-value explanation is not required, and the annotations cover the safety profile. However, for a tool that aggregates five data sources and computes derived risk figures, leaving both parameters unexplained (especially the refresh semantics) means an agent cannot confidently control freshness or the time window.

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 both parameters are undocumented in the schema, so the description carries the burden. It never mentions 'atualizar' (refresh/cache bypass) at all, and only obliquely hints at 'dias_antecedencia' via 'provas próximas' without stating that it controls the look-ahead window and defaults to 7 days. The coverage 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 names a specific artifact (a proactive academic-risk panel) and enumerates the four things it surfaces: absences approaching the 25% limit, grades needed for approval/AF, tasks by deadline and submission status, and upcoming exams plus library pending items. That makes it clearly the aggregated-risk sibling rather than a lookup tool like faltas, notas or tarefas, though it never explicitly states that relationship.

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: the framing as a 'painel proativo de riscos' suggests an overview/dashboard call rather than point lookups, but there is no explicit 'use this when you want a consolidated risk view instead of calling faltas/notas/tarefas separately', and no conditions for when not to use it.

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