Skip to main content
Glama
Sign In
sigaa-mcp

sigaa-mcp

by Pedromaia0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Histórico de turmas

get_all_classes

Retrieves all current and past enrolled classes grouped by academic period, helping you review a student's complete course history in SIGAA.

Instructions

All enrolled classes, current and past, grouped by period (Ver turmas anteriores).

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_all_classes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that results include current and past classes and are grouped by period, but it does not state read-only behavior, permissions, pagination, or the exact return structure.

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 description is a single concise sentence with the key scope details front-loaded. The parenthetical is somewhat terse and language-shifted, but overall it avoids unnecessary wording.

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 simple zero-parameter list tool with no output schema, the description gives the essential scope and grouping behavior. It could go further on output shape or access requirements, but it is largely complete for this level of complexity.

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?

The tool has zero parameters, so there are no parameter semantics to explain; the baseline for no parameters is 4. The description does not need to compensate for an input schema.

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 states the tool returns all enrolled classes, current and past, grouped by period. This is more specific than the name alone and distinguishes the scope from the singular sibling get_turma, though it lacks an explicit verb like 'list'.

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 implies the tool is for viewing class history, but it does not explicitly say when to use it instead of get_turma or any other sibling. The parenthetical 'Ver turmas anteriores' hints at historical viewing but is not clear usage guidance.

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