Skip to main content
Glama

faltas

Read-onlyIdempotent

Calculates per-discipline workload, recorded absences, the 25% regulatory limit under UFC Art. 113, and remaining 2-hour meetings to help students track attendance risk.

Instructions

Calcula detalhadamente para cada disciplina a carga horária, faltas registradas, limite regulamentar de 25% (Art. 113 do Regimento Geral da UFC) e encontros de 2h restantes.

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

Input Schema

NameRequiredDescriptionDefault
id_turmaNo
atualizarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered by structured data. The description adds useful domain rules (the 25% cap from the UFC Regimento Geral), but it says nothing about what 'atualizar' actually triggers — a cache-bypass or live refresh against the portal — which is the main behavioral question an agent would have.

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 well-formed sentence that front-loads the verb and then enumerates outputs; no filler. It is long but every clause names a distinct computed value.

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 explained, and the domain rule is well covered. However, for a tool with a refresh flag and an optional class-id filter, the absence of any guidance on those two inputs leaves the definition meaningfully incomplete.

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%, so the description carries the full burden, yet it never mentions 'id_turma' or how a per-turma scope relates to the per-disciplina output it describes. The 'atualizar' refresh flag is likewise unexplained, leaving both parameters to guesswork.

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 ('Calcula') and enumerates the exact computed values: carga horária, faltas registradas, the 25% regulatory limit (Art. 113), and remaining 2h meetings. An agent knows precisely what the tool returns, but there is no explicit differentiation from the sibling 'frequencia', which likely covers overlapping territory.

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?

There is no statement of when to use this versus alternatives, and no mention of prerequisites (e.g. an active matrícula or current semester). The reader must infer usage context entirely from the tool name and the sibling list.

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