Skip to main content
Glama

estudo

Read-onlyIdempotent

Builds a course-specific active study plan by cross-referencing UFC grade status, syllabus, professor materials, and exam dates to prioritize next steps.

Instructions

Organiza uma intervenção pedagógica e roteiro de estudo ativo para uma disciplina: diagnostica a situação de notas do estudante segundo o Regimento Geral da UFC (Art. 114), cruza o cronograma e a bibliografia do Plano de Curso com os materiais/slides postados pelo professor e a data da próxima prova, e estrutura uma sequência de estudo com recuperação ativa baseada nos documentos reais da turma.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id_turma": "<id_turma>"
    },
    "name": "estudo"
  }
}

Input Schema

NameRequiredDescriptionDefault
focoNoproxima_prova
id_turmaYes
atualizarNo
termo_topicoNo

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 readOnly, idempotent and non-destructive, so safety is covered. The description adds real context by revealing that this is a heavy multi-source aggregation (grades regulation + course plan + posted slides + exam date), which tells the agent it is expensive/derivative. It does not explain latency, whether it depends on the professor having posted materials, or what happens if data is missing – and the schema's 'atualizar' flag sits oddly next to readOnlyHint, though the description itself makes no write claim, so no contradiction.

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, but it is front-loaded with the core action and sequenced logically (diagnose → cross-reference → structure). No filler or repetition; the length is justified by the composite behavior, though it is harder to scan than a two- or three-sentence layout.

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?

Output schema exists, so return values need no explanation, and the one-sentence purpose covers the workflow well. But for a 4-parameter tool with 0% schema coverage and an ambiguous 'atualizar' flag, the definition leaves essential invocation details undocumented – an agent knows what the tool does but not how to configure it.

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 coverage is 0% and the description compensates almost not at all: it never names or explains 'foco', 'atualizar' or 'termo_topico'. The narrative loosely matches foco=proxima_prova and mentions a topic implicitly, but there is no statement of what each enum value selects or that termo_topico is required when foco=topico_especifico. Only 'id_turma' is inferable from 'para uma disciplina'.

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 composite action: diagnosing grade status under UFC Art. 114, cross-referencing the course plan schedule/bibliography with posted materials and the next exam date, and building an active-recall study sequence. The verb set (diagnostica, cruza, estrutura) is concrete and the resource is unmistakable. It only partially separates itself from siblings like notas/plano/diagnostico – the synthesis is implied rather than stated as 'unlike plano, this builds a plan'.

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 implied by the scenario ('para uma disciplina… próxima prova'), and the enumerated inputs hint at the preconditions (course plan, materials, exam date must exist). However, there is no explicit when-to-use/when-not guidance and no mention of the obvious alternatives (notas for raw grades, plano for the syllabus, avaliacoes for the exam list), so the agent must infer routing.

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