Skip to main content
Glama
Sign In
getcourse-mcp

getcourse-mcp

by skiddgoddamn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gc_list_training_groups

List access groups for a training by ID, optionally filtering by group name substring.

Instructions

Список групп доступа, связанных с тренингом (id + название). filter — подстрока по названию.

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": {
      "trainingId": "<trainingId>"
    },
    "name": "gc_list_training_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoПодстрока для фильтрации названий групп (регистронезависимо).
trainingIdYesID тренинга.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It indicates a read operation (listing) but does not explicitly state safety, authentication needs, or potential side effects. The description is adequate but not thorough.

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 concise sentences with no wasted words. The description is front-loaded with the core purpose, followed by parameter clarification.

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 tool with 2 parameters and no output schema, the description covers the main purpose and filter semantics. However, it lacks details on error handling (e.g., invalid trainingId), return format structure, and pagination, leaving some gaps.

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%, so baseline is 3. The description adds context that filter is a substring on name and output includes id+name, but these are partially covered by schema descriptions. No significant extra semantic value beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists access groups related to a training, returning id and name. The verb 'list' and resource 'training groups' are specific, and the tool is distinct from siblings like gc_list_user_groups.

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?

The description implies usage for retrieving groups by training, but does not explicitly guide when to use it versus alternatives or when not to use it. No exclusions or conditions are mentioned.

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