sigaa-mcp

Baixar arquivo da turma

download_file

Downloads a SIGAA course file by fileId and turma handle, saves it locally, and returns its path, filename, content type, and size.

Instructions

Download a file published in a turma (a lesson-topic material or an Arquivos entry) by its fileId. Saves it locally and returns the path, filename, content type and size. fileIds come from get_turma (topics[].materials[].fileId or files[].fileId).

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": {
      "frontEndIdTurma": "<frontEndIdTurma>",
      "fileId": "<fileId>"
    },
    "name": "download_file"
  }
}

Input Schema

Name	Required	Description	Default
`fileId`	Yes	The file id from get_turma
`frontEndIdTurma`	Yes	The turma handle from get_portal

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1Nov 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description must carry the full burden, and it does disclose the key side effect: the file is saved locally. It also describes the return payload (path, filename, content type, size), which tells the agent what it will get back. It omits what happens on repeated downloads (overwrite or duplicate), any permission constraints, and whether the local path is stable across calls.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and resource, then the return shape, then the parameter provenance. Nothing is redundant and each sentence adds an operationally useful fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter download tool with no output schema, the description covers the action, the source of the fileId, the local-save side effect, and the return fields. An agent has everything needed to call it correctly and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline would be 3, but the description adds real meaning about fileId's provenance by pointing to get_turma and naming the exact array paths it appears in. frontEndIdTurma is not explained beyond the schema, which prevents a higher score.

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 ('Download a file published in a turma') and narrows the scope to two source types: lesson-topic materials or Arquivos entries. It implicitly separates itself from download_participant_photo, but it never names that sibling, 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 Guidelines4/5

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

It states exactly where the required fileId comes from (get_turma, with the exact paths topics[].materials[].fileId and files[].fileId), which tells the agent how to actually use the tool in a workflow. It does not say when not to use it or what to do if the file is not a turma file, so there is no exclusion guidance.

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

Deploy Server