Skip to main content
Glama

get_calendario_academico

Retrieve a course's academic calendar, including term dates, consolidation, withdrawal, and enrollment deadlines; specify a semester such as '2026.2' or omit it for the current one.

Instructions

Calendário acadêmico do curso: período letivo, consolidação, trancamento, matrícula, etc.

Args:
    semestre: no formato '2026.2'. Se omitido, usa o semestre atual do portal.

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

Input Schema

NameRequiredDescriptionDefault
semestreNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose a useful non-obvious trait — omitting 'semestre' falls back to the portal's current semester — but says nothing about the response shape, whether historical semesters are available, or failure modes.

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?

Very short and front-loaded, with the resource and its contents in the first line and the argument detail after. The docstring-style 'Args:' block is slightly formal but the format example it carries earns its place.

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 single optional parameter, read-only getter with no output schema, the description covers what the tool returns conceptually (the enumerated calendar items) and how the optional argument behaves. Nothing critical to a correct invocation is missing, though the returned structure remains unspecified.

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?

Schema coverage is 0%, so the description must compensate, and it does: it supplies the concrete format '2026.2' and explains the default behavior when the argument is null. The only gap is that the lower/upper bound of valid semesters is not stated.

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?

Names a specific resource (calendário acadêmico do curso) and enumerates the concrete items it covers (período letivo, consolidação, trancamento, matrícula), which separates it from siblings like get_notas or get_turmas. It is clear what is being fetched, though the verb itself is only implied by the tool name rather than stated in the description.

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 description states the default when 'semestre' is omitted, which tells the agent it can call the tool with no arguments. There is no explicit guidance on when to prefer this tool over get_agenda or get_resumo_semana, and no mention of what happens with an invalid or future semester.

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