Skip to main content
Glama

avaliacoes

Read-onlyIdempotent

Lists scheduled exam and assessment dates, times, and descriptions for a Virtual Class using a class ID, with an option to refresh the data.

Instructions

Lista as datas, horários e descrições das provas e avaliações agendadas 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": "avaliacoes"
  }
}

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=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the scoping to Turma Virtual and the shape of returned data, but says nothing about what the atualizar flag does (e.g., cache bypass) or any freshness/rate-limit behavior.

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 front-loaded sentence with no filler, stating scope and return fields immediately. It is efficient, though its brevity is partly the reason the parameter behavior goes unexplained.

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 and annotations exist, so return values and safety need not be spelled out. For a two-parameter, read-only listing tool the description is minimally adequate, but the unexplained atualizar toggle and the absence of sibling guidance leave 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% for both parameters; id_turma is only identified by its title and atualizar has no description at all. The phrase "na Turma Virtual" loosely implies id_turma selects the class, but the semantic effect of atualizar=true remains entirely undocumented in both schema and 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?

The description gives a specific verb ("Lista") and resource ("provas e avaliações agendadas na Turma Virtual") and even enumerates the returned fields (datas, horários, descrições), so an agent knows exactly what it retrieves. It does not, however, contrast itself with plausible siblings such as agenda, calendario, or notas, leaving the agent to infer which is the exam-specific source.

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 or when-not-to-use guidance. The agent can infer that it fetches assessments for a class, but nothing says whether to prefer agenda/calendario for a broader schedule view or how this relates to notas.

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