Skip to main content
Glama

turma

Read-onlyIdempotent

Reads topics published on a Virtual Class main page and lists attached materials with their id_material for download, using a class ID and optional refresh.

Instructions

Lê os tópicos de aula publicados na página Principal da Turma Virtual e lista os materiais/arquivos anexados com seus respectivos identificadores id_material para download.

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

Input Schema

NameRequiredDescriptionDefault
id_turmaYes
atualizarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description adds useful scope context (only published topics from the main page; materials are exposed with download ids), but it says nothing about whether results are cached or what 'atualizar' changes at runtime, which is the main behavioral unknown for a read tool.

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 tight sentence that front-loads the resource (published lesson topics) and ends with the actionable payoff (materials plus id_material for download). No filler or repetition.

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?

The output schema carries the return shape and annotations carry the safety profile, so the description only needs to convey scope — which it does. What remains missing is minor but relevant: the meaning of 'atualizar' and any indication of how this differs from 'aula'.

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?

Only two parameters, one required ('id_turma'), and the description makes clear the tool operates on a specific class page, so the required key is semantically implied. The optional 'atualizar' flag is never explained, which is the one real gap given near-zero schema description coverage.

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 specific verbs ('lê', 'lista') and names concrete resources: published lesson topics on the Turma Virtual main page plus attached materials with their id_material identifiers. An agent can tell this is a class-content/material listing tool, though it never contrasts itself with the sibling 'aula', which likely covers lesson detail rather than published-topic material listing.

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 guidance on when to call this instead of 'aula', 'biblioteca' or 'baixar', nor any mention of prerequisites such as enrollment in the class. The description also gives no hint about when the 'atualizar' flag should be turned on, which is exactly the kind of selection guidance this tool needs.

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