Skip to main content
Glama

Grant Course Role

grant_course_role

Assign an admin-level teaching role (REVIEWER, TEST_CREATOR, or COURSE_MANAGER) to a user in a specific course; students should use tags instead.

Instructions

(Admin) Da un rol docente en un curso (REVIEWER, TEST_CREATOR, COURSE_MANAGER). No sirve para alumnos: usa tags.

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": "grant_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

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description's main added value is the admin prerequisite and the teacher-role scope. It says nothing about whether the grant is additive or replaces an existing role, whether it is idempotent, whether the user must already be enrolled, or what happens on conflict — all material for a permission-granting mutation.

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 filler: the admin qualifier and the core action come first, the role list follows, and the exclusion is last. Nothing could be removed without losing information.

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 3-required-param mutation with an output schema (so return values need not be described), the definition covers who may call it and which roles exist, which is minimally viable. The absence of any explanation of role semantics or grant/replace behavior leaves real gaps for an agent deciding how to invoke it correctly.

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 description coverage is 0%, so the description had room to add meaning, and it does re-enumerate the three role values — but this only restates the schema enum without explaining what REVIEWER, TEST_CREATOR or COURSE_MANAGER actually confer, and course_id/user_id are entirely unexplained. The enum repetition is a minor assist, not real compensation for the coverage gap.

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 states a specific verb and resource ('Da un rol docente en un curso') and enumerates the exact roles accepted (REVIEWER, TEST_CREATOR, COURSE_MANAGER). It also marks itself as an admin operation and carves out students as out of scope, so it is distinguishable from revoke_course_role and the tag tools, though it never names the revoke sibling explicitly.

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 gives an explicit exclusion — 'No sirve para alumnos: usa tags' — routing student enrollment to the tag-based tools, and the '(Admin)' prefix signals the required privilege level. It does not state the inverse case (when to use revoke_course_role instead of this), so the guidance is clear but not complete.

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