Skip to main content
Glama

frequencia

Read-onlyIdempotent

Read a course's daily attendance map and count the total absences recorded by the professor in the Virtual Class.

Instructions

Lê o mapa diário de frequência e contabiliza o total de faltas registradas pelo professor na Turma Virtual.

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": {
      "id_turma": "<id_turma>"
    },
    "name": "frequencia"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_turmaYes
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. The description adds the aggregation behavior (counts total absences rather than listing them), but it is silent on the 'atualizar' flag, which is notable for a tool annotated as read-only — the agent cannot tell whether it triggers a refresh against the source system.

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 front-loaded sentence with no filler; the action and the aggregation result are stated up front. It is efficient, though a second short clause on the refresh flag could have been added at little cost.

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 read-only profile is covered by annotations. However, for a tool with a refresh parameter of unclear semantics and an ambiguous boundary with 'faltas', the description leaves real gaps.

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 the description mentions no parameter at all — neither the required 'id_turma' nor the optional 'atualizar' with its default of false. The most consequential unknown, what 'atualizar=true' changes about the read, is left entirely undocumented.

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 verb pair (lê / contabiliza) and a specific resource (mapa diário de frequência, faltas na Turma Virtual), so the agent knows it reads attendance and returns an absence count. It does not differentiate itself from the sibling 'faltas', which plausibly covers overlapping ground.

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 explicit when-to-use statement, no when-not-to-use, and no mention of 'faltas' as the alternative. The only guidance is implicit in 'Lê o mapa diário de frequência', leaving the agent to infer that this is an aggregated per-class read.

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