Skip to main content
Glama

horario

Read-onlyIdempotent

Builds an ordered Monday-to-Saturday weekly class schedule from enrolled UFC classes, with an option to refresh the data.

Instructions

Constrói a grade horária semanal ordenada de segunda a sábado a partir das turmas matriculadas.

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

Input Schema

NameRequiredDescriptionDefault
atualizarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.1/5.0
Behavior3/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 elsewhere. The description usefully adds that the schedule is derived from enrolled classes and is ordered Monday through Saturday, but it leaves the 'atualizar' flag unexplained and gives no indication of what happens when no classes are enrolled or how the ordered result is composed.

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 that front-loads the produced artifact and its scope, with no filler. It could only be improved by spending a clause on the undocumented 'atualizar' parameter rather than leaving it silent.

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?

The tool is simple: one optional boolean parameter and an output schema, so the description does not need to explain return values. The main remaining hole is the meaning of 'atualizar' and any sibling-differentiation, which are moderate rather than critical gaps for a computed schedule view.

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 one parameter, 'atualizar', with 0% schema description coverage, and the description never mentions it. An agent cannot tell whether it forces a re-fetch, rebuilds a cached schedule, or persists changes — which matters given that the verb 'Constrói' suggests generation while the annotation declares read-only behavior.

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 artifact ('Constrói a grade horária semanal'), states the scope (Monday–Saturday, ordered) and the data source ('a partir das turmas matriculadas'). That is enough to distinguish it from generic listing tools, but it gives no hint about how it differs from likely near-siblings such as 'grade', 'semana' 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says what the tool produces but never says when to reach for it instead of the other schedule-related siblings. There are no exclusions, prerequisites, or alternative-routing guidance, so an agent must guess based on tool names alone.

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