Skip to main content
Glama

grade

Read-onlyIdempotent

Build and validate course prerequisite DAGs, match them with offered classes, and generate conflict-free semester schedules under selected decision profiles.

Instructions

Conselheiro e otimizador combinatório de matrícula: constrói e valida o grafo acíclico direcionado (DAG) de pré-requisitos e co-requisitos do curso, cruza com as turmas ofertadas no semestre e resolve o problema de satisfação de restrições (Branch-and-Bound) sem choque de horário sob 3 perfis de decisão (desbloqueio curricular, grade compacta e carga equilibrada).

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

Input Schema

NameRequiredDescriptionDefault
anoNo
periodoNo
atualizarNo
estrategiaNodiversificada
codigos_ignorarNo
max_disciplinasNo
turno_preferidoNoqualquer
codigos_desejadosNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.8/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 safety is covered. The description adds real behavioral context — that this is a Branch-and-Bound constraint solver operating over a DAG plus live semester offerings, which implies non-trivial compute cost — but it does not state expected latency, whether results are cached, or what 'atualizar' changes. 'Constrói e valida' could read as a write action, though in context it plausibly means building an in-memory model rather than persisting anything.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense run-on sentence with the core purpose front-loaded, so it is not padded, but the heavy jargon (DAG, Branch-and-Bound, perfis de decisão) packs multiple ideas into one clause and makes it harder to scan. The '3 perfis' enumeration is wasted wording that also happens to be inaccurate.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. But for an 8-parameter solver with zero schema documentation, the description should at minimum explain estrategia, max_disciplinas, codigos_ignorar/desejados and turno_preferido; it explains none, and its strategy count contradicts the enum.

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% across 8 parameters, so the description carries the full burden and does not meet it: ano, periodo, atualizar, max_disciplinas, codigos_ignorar, codigos_desejados and turno_preferido are never explained. Worse, the description says '3 perfis de decisão' and names only desbloqueio, compacta and equilibrada, while the estrategia enum actually has four values including 'diversificada' — a mismatch that actively misleads on the key parameter.

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 and resource — it builds and validates a prerequisite/co-requisite DAG, cross-references semester course offerings, and solves a constraint-satisfaction problem with no schedule conflicts. That is far more specific than a name like 'grade' alone, and it implicitly distinguishes itself from simple listing tools by describing an optimizer. It stops short of naming which sibling (matricula, horario, plano) it supersedes, so the differentiation is inferred rather than stated.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named. The mention of '3 perfis de decisão' gestures at use cases, but the description never says when an agent should pick this tool over matricula or horario, nor what prerequisites must hold before calling it.

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