Skip to main content
Glama
Sign In
sigaa-mcp

sigaa-mcp

by GallegoSz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_notas

Retrieves a student's semester grades, covering assessment units, recovery, final exam, absences, and final status, so you can review academic performance; use attendance data for ongoing semesters.

Instructions

Notas do aluno por semestre (unidades, recuperação, prova final, resultado, faltas, situação).

'faltas' só vem preenchido em disciplinas já consolidadas (semestres anteriores);
para o semestre em andamento use get_frequencia.

Args:
    semestre: filtra por um semestre, no formato '2026.2'. Se omitido, retorna todos.

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

Input Schema

NameRequiredDescriptionDefault
semestreNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose a genuinely important data-quality trait: the 'faltas' field is partial and only filled for consolidated semesters. It does not explicitly restate read-only semantics or output shape, but the output schema covers the return values.

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?

The parenthetical field list front-loads what the agent gets, and the caveat plus alternative tool follow immediately. The Args block is slightly redundant with the prose but remains short and scannable with no filler.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single optional-parameter read tool with an output schema, the definition covers purpose, filtering semantics, and the one data caveat an agent could otherwise misread. Nothing critical is missing, though expected behavior for empty results is not mentioned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: it specifies the '2026.2' format example and the default behavior when the parameter is omitted. The only gap is that non-matching or invalid semester values are not addressed.

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 resource and enumerates the returned contents (unidades, recuperação, prova final, resultado, faltas, situação), so an agent knows exactly what data this yields. It also distinguishes itself from get_frequencia for the 'faltas' field, though the verb itself is only implied by the get_ prefix.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit routing rule: 'faltas' is only populated for consolidated/prior semesters, and the current semester requires get_frequencia instead. It also clarifies the omission behavior for semestre (returns all). It does not address when to prefer this over closely related siblings such as get_situacao_notas or get_avaliacoes.

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

Deploy Server

Other Tools