Skip to main content
Glama

ofertas

Read-onlyIdempotent

Query offered class sections for a semester with decoded schedules, locations, instructors, and seat counts from SIGAA or the student class search.

Instructions

Consulta as turmas ofertadas no semestre (horários decodificados, locais, docentes e vagas) usando o portal público do curso no SIGAA ou a busca de turmas do discente.

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

Input Schema

NameRequiredDescriptionDefault
anoNo
periodoNo
id_cursoNo
atualizarNo
codigo_componenteNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely new behavior — that data can come from a public course portal or the student's own class search — but leaves unexplained whether results are cached and what `atualizar` changes about freshness.

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 dense sentence that front-loads the resource and then lists the payload fields, with no filler. It is efficient, though packing the two data sources into one clause makes the sentence harder to parse than necessary.

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 no explanation, but the input side is a real gap: five undocumented parameters with entirely unannotated schema, and defaults (2026, period 2) that an agent might not realize it can override. For a semester-scoped query tool this leaves too much to guesswork.

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% across five parameters, so the description carries the full burden and does not meet it: `ano`, `periodo`, `id_curso`, `atualizar`, and `codigo_componente` are never mentioned. An agent cannot tell from the text what `id_curso` selects or that `codigo_componente` narrows to a single course component.

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 and resource: 'Consulta as turmas ofertadas no semestre', and enumerates what the result contains (decoded schedules, locations, teachers, vacancies). It never names the sibling `turmas` or explains how this differs from it, so differentiation is left to inference.

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

Usage Guidelines3/5

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

It hints at two retrieval paths ('portal público do curso no SIGAA' or 'busca de turmas do discente'), which implies source selection, but never states when to prefer one over the other or when to use this tool instead of `turmas`, `horario`, or `grade`. Guidance is implied rather than explicit.

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