Skip to main content
Glama

list_training_participants

List learners enrolled in a training with their progress and scores, optionally filtered by completion status, to track participation and outcomes.

Instructions

List the learners enrolled in a training with their progress and score, optionally filtered by completion status.

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": {
      "training_id": "<training_id>"
    },
    "name": "list_training_participants"
  }
}

Input Schema

NameRequiredDescriptionDefault
completionNo
max_resultsNo
training_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; "List" implies a non-mutating read and the description usefully discloses that progress and score come back. It is silent on pagination, truncation at the default 500 / cap of 5000, and any permission requirements, which are exactly the behaviors an agent needs.

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 front-loaded sentence with no filler; every clause adds information about scope, payload, or filtering.

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 tool with no output schema, the description covers what is returned and how to filter, but the silent result cap and lack of any prerequisite guidance leave meaningful gaps relative to the 3-parameter surface.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and with three parameters the description only explains the completion filter; it says nothing about max_results (default 500, cap 5000) or that training_id must reference an existing training, leaving the limit behavior undocumented.

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 ("List the learners enrolled in a training") and names the payload returned (progress and score), which distinguishes it from roster-wide siblings like list_users.

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?

It notes the optional filter but does not say when to prefer this over list_users or the stored-result tools, nor any prerequisite such as needing a valid training_id from list_trainings.

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