Skip to main content
Glama

calendario

Read-onlyIdempotent

Query the UFC official university calendar for events, holidays, recesses, and enrollment or withdrawal deadlines using date ranges or search text.

Instructions

Consulta eventos, feriados, recessos e prazos de matrícula/trancamento no Calendário Universitário oficial da UFC.

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

Input Schema

NameRequiredDescriptionDefault
fimNo
textoNo
inicioNo
limiteNo
atualizarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.6/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered elsewhere. The description adds no behavioral detail beyond that: it does not explain what 'atualizar' does to the cached data, how 'limite' truncates results, or how the official source is consulted. With annotations in place, the remaining gaps keep this at a 2.

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 well-formed sentence with no filler, and it front-loads the resource categories. It is efficient, though it is arguably too short for the parameter surface it covers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because an output schema exists, return values do not need to be explained. However, for a tool with 5 undocumented parameters and multiple close siblings, the definition omits both parameter meaning and usage routing, so it is not complete enough for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 5 parameters (inicio, fim, texto, limite, atualizar), and the description names none of them. Since the schema is completely undocumented, the description should carry the burden of explaining formats and defaults, and it provides nothing.

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 gives a specific verb (Consulta) and a specific resource (eventos, feriados, recessos, prazos de matrícula/trancamento no Calendário Universitário oficial da UFC), which is clearly more than a restatement of the name 'calendario'. It does not distinguish itself from the sibling 'calendario_curso', which presumably reads a similar source, so it falls short of a 5.

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 definition gives no guidance about when to call this tool instead of alternatives such as calendario_curso, agenda, dia, semana, or avaliacoes. A reader can only infer that it is the general university calendar, which is weak guidance for routing among so many date-related siblings.

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