Skip to main content
Glama

baixar

Idempotent

Download professor-posted course materials from the Virtual Class to an isolated local folder and extract paginated text from PDF, TXT, or MD files for assisted study.

Instructions

Baixa de forma segura um arquivo/material postado pelo professor na Turma Virtual (slides, listas de exercícios, apostilas) para a pasta local isolada do estudante e extrai texto paginado (PDF/TXT/MD) para estudo assistido. 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>",
      "id_material": "<id_material>"
    },
    "name": "baixar"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_turmaYes
id_materialYes
pagina_finalNo
extrair_textoNo
pagina_inicialNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the write-but-safe profile is known. The description adds genuinely useful context beyond that: it writes into an isolated local student folder (safety/isolation), extracts paginated text and supports PDF/TXT/MD, and explicitly flags that texto_externo fields are third-party content, which is a trust warning an agent needs. It still does not say what happens on overwrite or repeat downloads.

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 sentences, front-loaded with the primary download action before the extraction detail. It is dense and slightly run-on, but no sentence is filler; the trust note at the end is compact and earns its place.

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 values need not be described, and annotations cover the safety profile. What is missing is parameter-level meaning and download mechanics (where exactly files land, overwrite/repeat behavior), which matters for a 5-parameter write tool with zero schema descriptions.

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 5 parameters, so the description carries the full burden and does not meet it. It never explains id_turma, id_material, pagina_inicial, pagina_final or extrair_texto; the mention of 'texto paginado' only loosely hints at the pagination parameters and defaults (1 and 10) are never surfaced.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (baixar) plus concrete resources (arquivo/material postado pelo professor na Turma Virtual) and enumerates examples (slides, listas de exercícios, apostilas). It also states the destination (pasta local isolada do estudante) and the secondary action (extrair texto paginado), leaving no ambiguity about what the tool does.

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 'para estudo assistido' and the mention of PDF/TXT/MD, so an agent can infer this is the tool for pulling course materials before studying them. However, there is no explicit when-to-use versus when-not guidance, no mention of alternatives among siblings such as biblioteca or aula, and no prerequisites stated.

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