Skip to main content
Glama

agenda

Read-onlyIdempotent

Retrieves a student's consolidated SIGAA class schedule, with an option to refresh the data from the source.

Instructions

Consulta a agenda consolidada de turmas do discente no 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": "agenda"
  }
}

Input Schema

NameRequiredDescriptionDefault
atualizarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.8/5.0
Behavior2/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 nothing about the 'atualizar' refresh behavior (does it hit SIGAA live, cache, rate-limit, or fail on offline?) or what 'consolidada' aggregates, which is the main behavioral question an agent would have.

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?

One short sentence with no filler, and the resource is front-loaded. It is efficient but so terse that the brevity borders on under-specification rather than true conciseness.

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 tool has only one optional parameter, keeping complexity low. Still, the undefined 'atualizar' semantics and the lack of any alternative routing leave the definition thinner than ideal for a tool with this many siblings.

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?

There is a single optional parameter, 'atualizar', with 0% schema description coverage, and the description never mentions it or explains what refreshing entails versus using cached data. The description therefore does not compensate for the schema gap on the only parameter present.

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 names a specific verb and resource ('Consulta a agenda consolidada de turmas do discente') plus the source system (SIGAA), so an agent knows it returns the student's consolidated class schedule. It does not explicitly distinguish itself from near-siblings such as horario, calendario, semana, or dia, so the differentiation is only implicit.

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 use this tool versus the many schedule-related siblings (horario, calendario, semana, dia, aula). The only usage signal is the word 'consolidada', which hints at an aggregated view but never states a selection rule or exclusion.

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