Skip to main content
Glama

Hilo Completo de Foro en EVA

eva_hilo_foro
Read-onlyIdempotent

Retrieves the complete thread and all ordered replies from an EVA course forum discussion using its discussion ID, so you can review the full debate context.

Instructions

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

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>"
    },
    "name": "eva_hilo_foro"
  }
}

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that results are ordered and include all replies, but says nothing about size, pagination, truncation or access requirements for large threads.

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?

One compact sentence with the operation and scope front-loaded and no filler. It could have used the remaining space for the pagination/alternatives gap, but nothing present is wasted.

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 retrieval tool with no output schema, the description adequately says what comes back at a high level (all posts, ordered). It omits how large threads are handled and what fields each message contains, which an agent would need to plan a response.

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 the single required parameter discusion_id is fully documented in the schema. The description adds no format, validation or sourcing detail beyond it, 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 resource ('el debate o hilo completo de un foro de cátedra en EVA') plus the scope of the return (all replies and messages, ordered). It implicitly differentiates from siblings like eva_foros (listing) and eva_responder_foro (posting), but never names them explicitly.

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 by the word 'completo' — an agent can infer this is for reading an entire thread rather than listing forums. There is no explicit when-to-use, when-not, or reference to an alternative sibling tool.

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