Skip to main content
Glama

Responder en Foro de Cátedra en EVA

eva_responder_foro

Publishes a reply to an EVA course forum thread after showing the full message and requesting user confirmation.

Instructions

Publica una respuesta en un foro de cátedra de EVA. Muestra el texto completo y requiere confirmación del usuario.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "discusion_id": "<discusion_id>",
      "mensaje": "<mensaje>"
    },
    "name": "eva_responder_foro"
  }
}

Input Schema

NameRequiredDescriptionDefault
mensajeYesMensaje exacto a publicar en el foro (máx 350 caracteres)
discusion_idYesID numérico del hilo o debate de foro

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": {
      -    "aprobado": {
      -      "type": "boolean"
      -    },
      -    "detalles": {
      -      "additionalProperties": {},
      -      "type": "object"
      -    },
      -    "exito": {
      -      "type": "boolean"
      -    },
      -    "instruccion": {
      -      "type": "string"
      -    },
      -    "mensaje": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "exito",
      -    "mensaje"
      -  ],
      -  "type": "object"
      -}New value: +null
  2. First observedv1.0.6

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=false, so the write nature is covered. The description adds genuinely new behavioral context beyond that: the full text is shown to the user and an explicit user confirmation is required before publishing — a confirmation gate the agent must respect. It does not warn that repeated invocations create duplicate posts (the non-idempotent consequence).

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 short sentences, zero filler, with the confirmation requirement front-loaded right after the action statement. Nothing redundant with the schema.

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 2-parameter write tool with full schema coverage and safety annotations, the essential shape is there, but the description says nothing about what the tool returns (post ID, URL) or what error conditions look like (closed thread, expired session, over-length message). With no output schema, a brief note on outcomes would have closed the gap.

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 coverage is 100% and both parameters carry descriptions (message with 1-350 char bounds, numeric thread ID), so the schema does the heavy lifting. The description adds no format, escaping or content constraints beyond it; 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?

Names a specific verb and resource ("Publica una respuesta en un foro de cátedra de EVA"), so an agent knows this writes a reply into a discussion thread. It does not differentiate from the read-side siblings eva_foros / eva_hilo_foro, nor state whether it can create new threads as well as replies.

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 only implied: the `discusion_id` parameter and the word "respuesta" suggest you reply to an existing thread. Nothing tells the agent when to prefer this over reading with eva_hilo_foro, nor any prerequisites (enrollment, enrollment role, course context).

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