Skip to main content
Glama
santinohicke

UCA MCP

by santinohicke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Foros y Avisos en EVA

eva_foros
Read-onlyIdempotent

Fetch recent institutional announcements and course forum messages tagged as security notices, optionally filtered by course ID, to keep users informed.

Instructions

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. 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, openWorldHint and idempotentHint, so the safety profile is covered. The description adds little beyond that, and the parenthetical '(etiquetados con aviso de seguridad)' is ambiguous — it is unclear whether results are filtered to security-flagged messages or merely carry that label. Cache behavior is disclosed only via the schema's forzar_refresco parameter.

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 and resource first and no filler. The trailing parenthetical is the only part that costs clarity rather than earning 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?

For a read-only listing tool with full schema coverage and clear annotations, the definition is mostly sufficient, but with no output schema the description should say what each item contains (course, date, flag) and resolve the 'aviso de seguridad' ambiguity.

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% — limit, curso_id and forzar_refresco (including the 45-60 s cache) are all documented in the schema. The description adds no meaning beyond that, 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 specific verb ('Obtiene') and two concrete resources ('avisos institucionales' and 'mensajes de foros de cátedra') scoped to the latest items. An agent can tell it apart from eva_hilo_foro (single thread) or eva_responder_foro (write), though the description never names those siblings explicitly.

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 when-to-use or when-not-to-use guidance, and no mention of alternatives such as eva_hilo_foro for reading a full thread. The recency wording ('últimos') only hints at the intended scenario.

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