Skip to main content
Glama

plano

Read-onlyIdempotent

Retrieves a course syllabus from Turma Virtual by class ID, covering methodology, assessments, class schedule with dates and topics, and bibliography.

Instructions

Lê o Plano de Curso / Programa de uma disciplina na Turma Virtual: metodologia, procedimentos de avaliação, cronograma de aulas (com datas e tópicos) e referências bibliográficas. Os campos texto_externo são conteúdo de terceiros.

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

Input Schema

NameRequiredDescriptionDefault
id_turmaYes
atualizarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3/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. The description adds genuinely useful context: a breakdown of what is returned and the caution that texto_externo fields contain third-party content, which matters for trust handling. It says nothing about what the boolean atualizar does behaviorally (e.g. bypassing a cache), which is the one trait an agent could get wrong.

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?

Two compact sentences, front-loaded with the resource and content list, with the third-party-content note placed after. No filler, though the second sentence is somewhat under-integrated and the atualizar gap suggests room was available for one more clarifying clause.

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?

An output schema exists, so return structure need not be spelled out, and the annotations cover the read-only safety profile. However, for a tool whose only non-trivial decision is whether to set atualizar, the description leaves that entirely unexplained, so it is not fully complete relative to its modest complexity.

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% for both parameters, so the description carries the full burden — and it explains neither. "de uma disciplina na Turma Virtual" loosely implies id_turma identifies the class, but atualizar (boolean, default false) is never mentioned, leaving the agent to guess whether it refreshes cached data or triggers anything else.

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 opens with a specific verb and resource ("Lê o Plano de Curso / Programa de uma disciplina na Turma Virtual") and enumerates the returned content: methodology, assessment procedures, class schedule with dates and topics, and bibliography. That is concrete enough to separate it from most siblings (agenda, aula, avaliacoes), though it never names an overlapping alternative explicitly.

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 when-to-use or when-not-to-use guidance and no mention of alternatives — the agent must infer from the content list that this is the tool for the discipline's course plan. No prerequisites (e.g. needing a valid id_turma from a listing tool) are stated.

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