Skip to main content
Glama
Sign In
sigaa-mcp

sigaa-mcp

by GallegoSz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_noticias

Retrieves news published by professors in a virtual class, including title and date, and supports filtering by discipline to locate relevant course updates.

Instructions

Notícias publicadas pelos professores na turma virtual (título e data).

Args:
    disciplina: parte do nome da disciplina (sem diferenciar acentos/caixa). Se omitido, todas.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_noticias"
  }
}

Input Schema

NameRequiredDescriptionDefault
disciplinaNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the response contents (title and date) and the all-subjects default, which is useful. It says nothing about permissions, whether "turma virtual" is a specific enrolled course, pagination, or how far back news is retrieved.

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?

Two compact elements: a one-line purpose with return fields, then a short Args block for the single parameter. Nothing is wasted and the purpose is front-loaded.

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 needn't be explained, and the single optional parameter is covered. Still, ambiguity about which course context "turma virtual" refers to and the absence of any read-only/permission framing leaves gaps for an agent deciding whether to call it.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate: it explains that disciplina is a partial name match, is accent- and case-insensitive, and defaults to all subjects. That is genuinely valuable, but the exact matching/tokenization rules and whether multiple matches are allowed remain unspecified.

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?

"Notícias publicadas pelos professores na turma virtual" names a specific resource (news/announcements posted by professors) and even the returned fields (título e data). It is clearly distinct from siblings like get_notas or get_tarefas, though it never explicitly contrasts itself with them.

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 statement of when to call this versus alternatives or what prerequisites exist. "Se omitido, todas" describes the effect of omitting a parameter, which is scope behavior rather than usage guidance.

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

Deploy Server

Other Tools