Skip to main content
Glama

notas

Read-onlyIdempotent

Reads the grade table (AP1, AP2, AP3) for a UFC Virtual Class, returning partial average, consolidated absences, and the student's current status by class ID.

Instructions

Lê a tabela de notas das unidades (AP1, AP2, AP3), média parcial, faltas consolidadas e situação 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": "notas"
  }
}

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 safety is covered by structured data. The description adds the data scope (grades, partial average, consolidated absences, class status) but says nothing about freshness, caching, or what the 'atualizar' flag changes behaviorally.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that lists the returned fields with zero filler. Nothing redundant, nothing buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, but the definition is still incomplete for the input side: with 0% schema coverage and no parameter discussion, an agent cannot tell what 'id_turma' expects or when to set 'atualizar' to true.

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 mentions neither parameter. The required 'id_turma' and especially the 'atualizar' boolean (presumably a refresh-from-source flag) are left entirely opaque, which is a real gap for a two-parameter tool.

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 ('Lê') plus a concrete resource ('tabela de notas') and enumerates the data returned: AP1/AP2/AP3 grades, média parcial, faltas consolidadas and situação na Turma Virtual. That makes it distinguishable from siblings like faltas or avaliacoes at a glance, though it never explicitly names those siblings to sharpen the boundary.

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 when-to-use or when-not-to-use guidance, and no alternative is named. The reader must infer that this is the tool for grade lookups rather than, say, faltas or ira, purely from the field list.

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