Skip to main content
Glama

turmas

Read-onlyIdempotent

Fetches current-semester enrolled classes with codes, names, IDs, default locations, and decoded meeting times; set atualizar to refresh cached data.

Instructions

Retorna a lista de turmas matriculadas no semestre atual com código, nome, id_turma, local padrão e horários decodificados.

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

Input Schema

NameRequiredDescriptionDefault
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 scope (current semester only) and notes that schedules come pre-decoded, but it is silent on the 'atualizar' flag — presumably a cache-refresh toggle — which is exactly the behavioral nuance an agent needs for a read-only tool.

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 well-formed sentence with the scope and return fields front-loaded and no filler. It is efficient, though it spends its words entirely on output and none on the one input it accepts.

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 the field enumeration in the description is a bonus rather than a necessity. For a simple one-parameter read tool this is close to adequate, but the unexplained 'atualizar' parameter and the absence of any guidance on when to prefer this over sibling listing tools leaves a real gap.

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 the single parameter 'atualizar' (boolean, default false), and the description never mentions it. With one undocumented parameter the description needed to explain what refreshing does (bypass cache, hit the portal again), and it does not.

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?

States a specific verb and resource ('Retorna a lista de turmas') scoped to the current semester, and enumerates the returned fields (código, nome, id_turma, local padrão, horários decodificados). It does not differentiate itself from plausible siblings like 'listagem', 'agenda' or 'horario', so it falls short of a 5.

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?

The description gives no when-to-use guidance, no exclusions, and never names an alternative tool. An agent must infer from the name alone that this is for class/enrollment listings rather than schedules or grades.

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