Skip to main content
Glama
Sign In
UTN FRM MCP

UTN FRM MCP

by BautistaAlosMartorell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_forums

Read-only

Lists all forums in a specific Moodle course, including announcements, news, and Q&A areas, using the course ID, URL, or name.

Instructions

Lista todos los foros disponibles dentro de una materia (avisos, novedades, consultas, etc.).

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": {
      "course_id": "<course_id>"
    },
    "name": "list_forums"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYesMateria: ID numérico (de list_courses), URL del curso o su nombre, por ejemplo "126" o "ciencia de datos". Si el nombre es ambiguo se informan las candidatas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.1
    • changedInput schema / properties / course_id / description
      Previous value: -"ID numérico de la materia para listar todos los foros disponibles"New value: +"Materia: ID numérico (de list_courses), URL del curso o su nombre, por ejemplo \"126\" o \"ciencia de datos\". Si el nombre es ambiguo se informan las candidatas."
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the scope of what is listed (avisos, novedades, consultas), and says nothing about ordering, empty results, or whether it requires enrollment/authentication.

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 front-loaded sentence with no filler. It is efficient, though arguably under-specified rather than optimal for a tool whose output feeds several forum-related siblings.

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 simple read-only list tool with full schema coverage and annotations, the essentials are present, but there is no output schema and the description does not hint at the return contents (forum ids/names) that the agent must carry into get_forum_discussions. Adequate but with a clear 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 description coverage is 100% and the single course_id parameter is fully documented in the schema, including ID/URL/name formats and ambiguity handling. The description adds no parameter meaning beyond the schema, so the baseline of 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?

The description uses a clear verb + resource ("Lista todos los foros disponibles dentro de una materia") and the parenthetical names representative forum types, so the agent knows exactly what is returned. It does not, however, distinguish itself from siblings such as get_forum_discussions, which is the natural companion call.

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: an agent can infer this is the entry point before get_forum_discussions, but the description never states when to use this instead of that sibling or that a course_id must come from list_courses. No exclusions or prerequisites are given.

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