Skip to main content
Glama

Foros y Avisos en EVA

eva_foros
Read-onlyIdempotent

Retrieves the latest institutional announcements and course forum messages flagged as security notices, with optional course filtering and a configurable message limit to keep you informed of key updates.

Instructions

Obtiene los últimos avisos institucionales y mensajes de foros de cátedra (etiquetados con aviso de seguridad).

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": "eva_foros"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoCantidad máxima de mensajes (máx 50) (por defecto: 10)
curso_idNoID del curso (opcional)
forzar_refrescoNoSi es true, ignora la caché de 45-60 s y consulta de nuevo (por defecto: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.1.0
    • removedInput schema / properties / forzar_refresco / default
      Removed value: -false
    • changedInput schema / properties / forzar_refresco / description
      Previous value: -"Si es true, ignora la caché de 45-60 s y consulta de nuevo"New value: +"Si es true, ignora la caché de 45-60 s y consulta de nuevo (por defecto: false)"
    • removedInput schema / properties / limit / default
      Removed value: -10
    • changedInput schema / properties / limit / description
      Previous value: -"Cantidad máxima de mensajes (máx 50)"New value: +"Cantidad máxima de mensajes (máx 50) (por defecto: 10)"
  2. Changed9 schema fields changedv1.0.8
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / curso_id / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / curso_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / curso_id / minimum
      Added value: +1
    • addedInput schema / properties / forzar_refresco
      Added value: +{
      +  "default": false,
      +  "description": "Si es true, ignora la caché de 45-60 s y consulta de nuevo",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / limit / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "foros": {
      -      "type": "array"
      -    },
      -    "instruccion": {
      -      "type": "string"
      -    },
      -    "total": {
      -      "type": "number"
      -    },
      -    "truncado": {
      -      "type": "boolean"
      -    }
      -  },
      -  "required": [
      -    "foros",
      -    "total"
      -  ],
      -  "type": "object"
      -}New value: +null
  3. First observedv1.0.6

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is fully covered and the description need not restate it. Beyond that it adds only one behavioral trait, that messages are tagged with a security notice, without explaining what that tagging means or how it surfaces. Caching behavior (45-60 s) is disclosed in the schema for forzar_refresco rather than in the description.

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?

A single front-loaded sentence with the verb first and no filler. It is appropriately sized for a simple list tool, though the cryptic trailing parenthetical costs some clarity.

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?

With no output schema, the description carries the burden of describing returns, and it only names the content types without indicating ordering, result shape, or how many messages come back by default. Safety and side-effect behavior are adequately covered by annotations, so the gap is limited to return-value detail.

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 100% and all three parameters (limit, curso_id, forzar_refresco) carry their own descriptions including defaults and the cache window. The prose adds no parameter-level information such as filtering semantics for curso_id or ordering relative to limit, so the baseline 3 applies.

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 concrete verb ("Obtiene") and concrete resources (avisos institucionales, mensajes de foros de cátedra) with a recency qualifier ("últimos"). The agent can distinguish it from eva_responder_foro by the read-only listing intent, though the boundary with eva_hilo_foro (reading a specific thread) is not spelled out. The parenthetical "etiquetados con aviso de seguridad" is somewhat opaque and slightly muddies the resource definition.

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, or alternative routing. The agent must infer that this is the right tool when the user asks about recent announcements, and nothing tells it to prefer eva_hilo_foro for a single thread or eva_contenido_curso for course material. Usage is only implied by the phrase "últimos avisos".

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