LearningSuite MCP Server

learningsuite_remove_badges_from_user

Remove specific badges from a user's profile by passing user ID and badge IDs. Use this to correct badge assignments or manage user achievements.

Instructions

Remove badges from a user

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": {
      "userId": "<userId>",
      "badgeIds": "<badgeIds>"
    },
    "name": "learningsuite_remove_badges_from_user"
  }
}

Input Schema

Name	Required	Description	Default
`userId`	Yes	User ID
`badgeIds`	Yes	Array of badge IDs

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden. It simply restates the tool name ('Remove badges from a user') and adds no behavioral details such as whether removal is permanent, if it can be undone, required permissions, or potential side effects.

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?

The description is a single concise sentence, front-loaded with the action, containing no fluff. However, it is a near-verbatim copy of the tool name, making it somewhat under-specified despite being concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple mutation tool with no annotations and no output schema, the description is minimal. It lacks information about return values, error handling, or behavioral nuances, and does not provide enough context beyond the schema for an agent to fully predict tool behavior.

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?

The input schema has 100% coverage with descriptions for both userId and badgeIds. The description adds no extra parameter meaning, so the baseline score of 3 is appropriate since the schema already documents the parameters adequately.

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 action (remove) and the resource (badges from a user), making the tool's purpose immediately obvious. It also distinguishes from the sibling tool 'learningsuite_assign_badges_to_user' by being its inverse operation.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention it is the counterpart to 'assign_badges_to_user' or give context on use cases, exclusions, or prerequisites.

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

Deploy Server