Skip to main content
Glama

calendario_curso

Read-onlyIdempotent

Retrieves a course-specific SIGAA calendar for enrollment and processing periods, helping you check key undergraduate dates by course ID.

Instructions

Consulta o calendário específico de períodos de matrícula e processamento de um curso de graduação no portal público do SIGAA.

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

Input Schema

NameRequiredDescriptionDefault
id_cursoNo
atualizarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.3/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 needs no restating. The description adds only that the data comes from SIGAA's public portal, but says nothing about the meaning of `atualizar`, caching/staleness of results, or failure modes when scraping a public portal.

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 front-loaded sentence that identifies the resource and its scope with no filler. Nothing redundant, nothing buried.

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 return values need not be explained, and the read-only annotations cover safety. However, for a tool with two undocumented optional parameters, the definition omits any guidance on the refresh flag or on the distinction from the generic calendar sibling, leaving real gaps.

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 both parameters, so the description must carry the burden and it does not. Neither `id_curso` (what form the course identifier takes, or the default when omitted) nor `atualizar` (what refreshing implies, whether it bypasses a cache) is addressed; only the prepositional phrase "de um curso" hints at course selection.

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 a specific verb ("Consulta") plus a precise resource ("calendário ... de períodos de matrícula e processamento") scoped to "um curso de graduação" on the public SIGAA portal. This is clearly distinguishable from a generic calendar tool, although it never names the sibling it contrasts with.

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?

Usage is only implied: the word "específico" suggests this is the per-course variant rather than the general calendar, but no explicit when-to-use, when-not-to-use, or prerequisites are stated. There is also no guidance on when a refresh (the `atualizar` flag) would be appropriate.

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