Skip to main content
Glama

Revoke Course Role

revoke_course_role
DestructiveIdempotent

Revoke a user's course role (REVIEWER, TEST_CREATOR, or COURSE_MANAGER) as an admin; the change is reversible by granting the role again.

Instructions

(Admin) Quita un rol docente de un curso. Reversible con grant_course_role.

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": {
      "course_id": "<course_id>",
      "user_id": "<user_id>",
      "role": "<role>"
    },
    "name": "revoke_course_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
user_idYes
course_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds two things annotations cannot: that the caller must be an admin, and that the effect is recoverable through grant_course_role, which softens the destructive signal and is valuable de-risking information.

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 short sentences, zero waste, with the admin restriction front-loaded and the reversal path attached immediately after the action.

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?

An output schema exists, so return values need no explanation, and the auth/reversibility context is present. But for a three-parameter destructive mutation with no schema documentation, leaving user_id and the role enum unaddressed keeps it only minimally sufficient.

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 description coverage is 0%, so the description carries the full burden, yet it only gestures at role and course and never mentions user_id at all — the target of the revocation is only implied. No enum values, id formats, or permission scoping for the role parameter are given beyond the phrase "rol docente".

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?

"Quita un rol docente de un curso" states a specific verb (revoke) plus resource (a teaching role on a course) and immediately names the inverse sibling grant_course_role, so the agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the admin prerequisite and, crucially, tells the agent the operation is reversible via grant_course_role, which is the key decision context. It stops short of naming when a caller should prefer course_access or update_course instead, so it is clear context rather than full when/when-not guidance.

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