Skip to main content
Glama

avisos

Read-onlyIdempotent

Reads professor announcements and notices from a UFC Virtual Class by class ID, with an option to refresh cached results.

Instructions

Lê os comunicados e avisos publicados pelo professor na Turma Virtual. 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": "avisos"
  }
}

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 a genuinely useful warning that texto_externo fields contain third-party content, but says nothing about caching or what the 'atualizar' flag changes behaviorally.

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; the core purpose is front-loaded. The second sentence pivots to return-value context rather than parameter meaning, which is slightly misplaced but still 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 the third-party content note is a good addition. However, with two parameters at 0% schema coverage and no usage guidance, an agent still lacks enough to invoke it confidently, especially regarding 'atualizar'.

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 explains id_turma (scope/format) or atualizar (presumably forces a refresh). The only field it discusses, texto_externo, is an output field rather than an input, so the input parameters remain undocumented.

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?

States a specific verb and resource: reads ('Lê') the announcements/notices ('comunicados e avisos') posted by the professor in the Turma Virtual. It is clear what the tool returns, though it does not explicitly differentiate itself from potential siblings such as noticias or alertas.

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?

No when-to-use guidance, no exclusions, and no named alternatives among the many sibling tools (noticias, alertas, agenda). The only implied context is that a class id is required, which the agent must infer from the schema.

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