Skip to main content
Glama
santinohicke

UCA MCP

by santinohicke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Hilo Completo de Foro en EVA

eva_hilo_foro
Read-onlyIdempotent

Retrieve a complete EVA Moodle course forum thread, including every reply and message in order, to review or analyze class discussions.

Instructions

Obtiene el debate o hilo completo de un foro de cátedra en EVA Moodle, incluyendo todas las respuestas y mensajes ordenados.

Input Schema

NameRequiredDescriptionDefault
discusion_idYesID numérico del debate o discusión del foro en EVA

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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 / discusion_id / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / discusion_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / discusion_id / minimum
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "discusionId": {
-      "type": "number"
-    },
-    "posts": {
-      "type": "array"
-    },
-    "totalPosts": {
-      "type": "number"
-    }
-  },
-  "required": [
-    "discusionId",
-    "totalPosts",
-    "posts"
-  ],
-  "type": "object"
-}New value: +null
  2. First observedv1.0.6

TDQS

A3.6/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 usefully adds that replies are included and ordered, but says nothing about pagination, truncation of very long threads, or depth limits – relevant for an open-world read.

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?

One sentence, zero waste, with the resource and completeness guarantee front-loaded. Nothing to trim and nothing buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only tool with annotations and full schema coverage, the description covers what is returned (all replies, ordered). It could go further on thread size or what happens with nested replies, but there is no output schema so the shape statement carries reasonable weight.

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?

There is a single parameter with 100% schema description coverage, so the baseline is 3. The description's "debate o hilo" phrasing reinforces the schema meaning of discusion_id but adds no format, source, or lookup guidance beyond it.

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?

The description states a specific verb and resource ("Obtiene el debate o hilo completo de un foro") and adds scope (all replies, ordered). It implicitly separates itself from eva_foros (listing) and eva_responder_foro (posting) by emphasizing "hilo completo," though it never names those siblings.

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

Usage Guidelines3/5

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

Usage is implied: use this when you need the full thread rather than a forum listing. There is no explicit when-to-use, no prerequisites, and no named alternative (eva_foros vs eva_responder_foro), so an agent must infer the routing from the purpose statement alone.

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