Skip to main content
Glama

tarefas

Read-onlyIdempotent

Lists assignments and tasks for a specified Turma Virtual class, returning titles, descriptions, deadlines, and submission status.

Instructions

Lista as tarefas e trabalhos da Turma Virtual com título, descrição, prazo de entrega e status de envio. 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": "tarefas"
  }
}

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, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful trust warning that texto_externo fields are third-party content, but says nothing about what the atualizar flag does behaviorally (refresh vs cached read) or about any rate/scope limits.

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 tight sentences with no filler, and the core listing behavior is front-loaded before the third-party content caveat. The caveat earns its place as a trust/safety note rather than padding.

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 the description need not explain return values, and the third-party content warning is a meaningful addition. However, for a tool whose schema has zero description coverage, leaving both parameters undocumented — especially the non-default atualizar flag — leaves a real gap before invocation.

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%, so the description carries the full burden, yet it never mentions either parameter. id_turma is only obliquely implied by "Turma Virtual", and atualizar (default false) is entirely unexplained even though toggling it likely changes whether a fresh fetch occurs.

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 verb and resource ("Lista as tarefas e trabalhos da Turma Virtual") and even enumerates the returned fields (título, descrição, prazo, status de envio). It does not differentiate from siblings such as avaliacoes, pendencias, or agenda, which also surface assignment-like data.

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, when-not-to-use, or named alternative. The agent must infer from the name and the "Turma Virtual" phrasing that this lists assignments for a given class, and is given no cue about preferring pendencias or avaliacoes in any situation.

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