Skip to main content
Glama

ics

Idempotent

Exports UFC semester class schedules and University Calendar events to an iCalendar file in the user's documents folder, optionally refreshing the data.

Instructions

Exporta a grade horária das turmas do semestre e os eventos do Calendário Universitário em um arquivo iCalendar padrão RFC 5545 (.ics) na pasta de documentos do usuário.

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

Input Schema

NameRequiredDescriptionDefault
atualizarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, and the description usefully adds that a file is written into the user's documents folder in a specific standard format. However, it does not say whether an existing .ics file is overwritten, where exactly the file lands, or what happens to previously exported data — material for a writing tool.

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 front-loaded sentence that states the action, both data sources, the format standard, and the destination with no filler. It is dense but every clause carries information; only the missing elaboration on "atualizar" keeps it from being ideal.

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

Completeness5/5

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

No, wait — for a tool that writes a file, the description covers what is exported, in what format, and to where, and an output schema exists so return values need not be explained. The remaining gap, the semantics of the "atualizar" flag and overwrite behavior, is real but limited to one optional parameter.

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?

The single parameter "atualizar" (boolean, default false) has 0% schema description coverage and is not mentioned at all in the description, so an agent cannot tell whether it means refresh existing data, overwrite the exported file, or force a regeneration. With one optional param and minimal schema help, the description should carry this meaning and does not.

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 specific verb ("Exporta") and two concrete resources (a grade horária das turmas do semestre and University Calendar events) plus the output artifact (.ics, RFC 5545, documents folder). The purpose is unambiguous, though it never explicitly contrasts itself with display-oriented siblings like grade or calendario.

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: an agent can infer this is the tool to call when a user wants a portable/importable calendar file, because the description names the file format and destination. No when-not-to-use conditions, prerequisites, or alternatives (e.g. showing the schedule on screen versus exporting it) are stated.

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