Skip to main content
Glama

Create Course

create_course

Create a new course with a name and description, optionally assigning a teacher and institution, then link a tag to make it visible to students.

Instructions

(Admin) Crea un curso. Para que los alumnos lo vean, asócialo a una tag con link_tag_to_course.

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": {
      "name": "<name>",
      "description": "<description>"
    },
    "name": "create_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
teacher_idNo
descriptionYes
institution_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive write, and the description usefully adds that admin rights are required and that an untagged course is invisible to students. It says nothing about name uniqueness, what happens with the optional teacher_id/institution_id defaults, or what is returned.

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 with zero waste: the action and permission level come first, then the practical consequence and the next step. Nothing is redundant.

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?

The output schema removes the need to describe return values, and the admin/tagging context covers the main workflow risk. However, with 0% parameter documentation on a four-parameter creation tool, the definition is not fully sufficient for confident invocation.

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% across four parameters, so the schema supplies only names and types, and the description adds no meaning for any of them. Terms like teacher_id, institution_id, and the null defaults are left entirely for the agent to guess.

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 opens with a specific verb+resource ('Crea un curso') and adds an admin scope qualifier, so an agent can tell it apart from update_course or delete_course. It stops short of explicitly naming what it is not, but the creation intent is unambiguous.

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 both a prerequisite ('(Admin)') and the required follow-up step: the course must be linked to a tag via link_tag_to_course for students to see it, which routes the agent to the correct sibling. It does not state when not to use it (e.g. duplicates or existing courses), but the context is clear.

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