Skip to main content
Glama

Leer avisos y foros

leer_avisos_foro

Retrieve latest forum posts from a course, focusing on professor announcements about schedule changes and assignments. Optionally include student discussion forums.

Instructions

Devuelve las últimas publicaciones de los foros de una materia. Por defecto trae solo los foros de avisos y novedades, que es donde los profesores comunican cambios de fecha y consignas.

Usá esta herramienta cuando pregunten si hay novedades o avisos del profesor. Pasá todos_los_foros en true solo si además quieren ver los foros de consultas entre estudiantes, que suelen ser muchos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limiteNoCuántas publicaciones traer por foro (por defecto 10)
courseidYesID de la materia, obtenido de listar_materias
todos_los_forosNoIncluir también los foros de consultas (por defecto false)
Behavior4/5

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

Without annotations, the description covers default behavior (only news forums) and the effect of 'todos_los_foros', noting that student forums are numerous. It does not detail return format or side effects, but for a read tool this is adequate.

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?

The description is concise with two clear sentences plus usage instructions. It is front-loaded with purpose and contains no redundant information.

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?

Given no output schema, the description sufficiently explains what the tool returns (latest posts) and covers the key parameter behavior. It is complete for its simplicity.

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 has 100% description coverage, so baseline is 3. The description adds context: default forum scope, association of courseid with 'listar_materias', and guidance on 'todos_los_foros'. This extra information justifies a score of 4.

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 clearly states it returns the latest forum posts of a subject, specifying default behavior (news and announcements) and optional all forums. It distinguishes from sibling tools by focusing on forums.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly advises to use when asked about news or teacher announcements, and describes when to use the 'todos_los_foros' parameter (only if student consultation forums are desired). Provides explicit usage scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/brujoh88/MCP-TUPAD'

If you have feedback or need assistance with the MCP directory API, please join our Discord server