Skip to main content
Glama

semana

Read-onlyIdempotent

Builds a seven-day overview from a start date using one SIGAA session, combining class schedules, assignment deadlines, university calendar events, and restaurant menus.

Instructions

Agrega 7 dias consecutivos a partir da data inicial com uma única sessão SIGAA, cruzando grade horária, prazos de atividades, eventos do Calendário Universitário e cardápios do RU.

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

Input Schema

NameRequiredDescriptionDefault
inicioNo
atualizarNo
restauranteNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.2/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 safety is covered. The description adds genuinely new behavior: all four sources are fetched in a single SIGAA session, which tells the agent this is one round-trip rather than four. It does not explain what happens when a source is unavailable or what the 'atualizar' flag changes behaviorally.

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?

A single dense sentence with the scope front-loaded and no filler. It is slightly compressed for the amount of information it carries, but every clause earns its place.

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 read-only annotations cover safety. Still, for a three-parameter tool with zero schema documentation, leaving one parameter and the whole data-availability behavior unexplained leaves the agent guessing.

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%, so the description must carry parameter meaning and it only partially does: 'a partir da data inicial' maps to inicio and 'cardápios do RU' hints at restaurante. The 'atualizar' boolean is never mentioned anywhere, and no formats, defaults or filtering semantics are given for any of the three parameters.

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?

States a concrete operation (aggregate 7 consecutive days from a start date) plus the four data sources it crosses: schedule, deadlines, university calendar and RU menus. That is specific enough to know what the tool returns, but it never distinguishes itself from the single-day sibling or from cardapio_semana, so sibling differentiation is absent.

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: a 7-day window anchored on a start date suggests 'use this for a weekly overview rather than a single day', but the description never says when to prefer it over dia, agenda or cardapio_semana, nor any prerequisites beyond the implicit SIGAA login.

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