getcourse-mcp

Overview Schema Source Related Servers Discussions Admin

gc_add_to_groups

Add an existing user to multiple groups by email without removing them from other groups. Use dryRun to preview changes before saving.

Instructions

Добавить существующего пользователя в группы через карточку (чисто, без импорта; сохраняет остальные группы). dryRun — предпросмотр.

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": {
      "email": "<email>",
      "groupIds": "<groupIds>"
    },
    "name": "gc_add_to_groups"
  }
}

Input Schema

Name	Required	Description
`email`	Yes	Email существующего пользователя.
`dryRun`	No	Показать изменение без сохранения.
`groupIds`	Yes	ID групп, в которые добавить (= выдать доступ).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 10, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The description discloses that the operation is clean (preserves other groups) and offers a dry-run preview. However, without annotations, it lacks details on failure modes, permissions, or side effects beyond what is stated.

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?

The description is extremely concise, consisting of two short sentences. Every word earns its place, and the key points are front-loaded.

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 3-parameter tool without output schema, the description adequately covers the core action and the dryRun feature. However, it lacks information on return behavior, error conditions, and fails to differentiate from similar sibling tools.

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 description adds no new information beyond the parameter descriptions in the schema. Baseline 3 is appropriate.

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 clearly states the tool adds an existing user to groups, preserving other groups and without import. However, it does not differentiate from the similarly named sibling 'gc_add_user_to_groups', which may cause confusion.

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?

The description gives no explicit guidance on when to use this tool versus alternatives. It mentions dryRun for preview but no when-not-to-use or prerequisites.

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