getcourse-mcp

by skiddgoddamn

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

gc_list_user_groups

Retrieve groups a user belongs to, with optional filter by group name. Returns group IDs and names.

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

Input Schema

Name	Required	Description	Default
`email`	Yes	Email пользователя.
`filter`	No	Подстрока для фильтрации названий групп (регистронезависимо).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided. Description mentions return fields (id, name) and filter behavior (case-insensitive substring match). No disclosure of pagination, limits, or authentication 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?

Two concise sentences. First sentence states purpose and output, second explains the filter parameter. No wasted words.

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?

With 2 parameters and no output schema, the description covers essential behavior. Could mention empty result case, but adequate for a simple list tool.

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 descriptions are already present. The description adds only 'регистронезависимо' (case-insensitive) to filter, which is a minor addition.

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 groups a user belongs to, returning id and name. It distinguishes from sibling add/remove/check tools.

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 listing a user's groups with an optional filter. It lacks explicit guidance on when to use vs alternatives or prerequisites.

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