Skip to main content
Glama

ver_discusion

Retrieves a complete Moodle forum discussion, including the announcement, replies, and attachments, by discussion ID.

Instructions

Muestra una discusión de foro completa (anuncio y respuestas) con sus adjuntos.

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

Input Schema

NameRequiredDescriptionDefault
discusionYesId de la discusión (aparece en anuncios)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; 'Muestra' implies a read-only retrieval but that is never stated as a guarantee. It does add real value by disclosing the shape of the result (announcement plus replies plus attachments), yet says nothing about access restrictions, what happens with an invalid or inaccessible id, or whether long threads are truncated.

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?

A single short sentence with the resource and its contents front-loaded and no redundant phrasing. Every clause contributes information.

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 one-parameter read tool with no output schema, the description covers what the result contains (announcement, replies, attachments), which is the main thing an agent needs to know. The remaining gaps are about access behavior and error cases rather than about how to invoke it.

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 the single 'discusion' parameter is already documented as the discussion id that appears in announcements. The description adds nothing beyond that, so the baseline 3 for schema-covered parameters 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?

The description names a specific verb ('Muestra') and resource ('discusión de foro completa') and clarifies the payload: the announcement, its replies, and attachments. It is distinct from the 'anuncios' sibling in that it returns one full thread rather than a listing, though it never states that contrast 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, no mention of prerequisites such as enrollment or permissions, and no pointer to alternatives like 'anuncios' for browsing. The intended use (fetch one thread by id) is only inferable from the text.

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