Skip to main content
Glama

Update Course

update_course

Modify a course's name, description, teacher, or institution and retrieve the previous values for auditing or rollback.

Instructions

(Admin) Cambia nombre, descripción, profesor o institución de un curso. Devuelve los valores previos.

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>"
    },
    "name": "update_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
course_idYes
teacher_idNo
descriptionNo
institution_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare a non-destructive write, and the description adds two traits beyond them: an admin/authorization requirement and the fact that prior values are returned (useful for rollback). It stops short of saying whether omitted or null fields are left untouched or cleared, and what the response shape is.

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?

Two short sentences with the admin scope and the mutation front-loaded and the return-value note second; nothing is redundant. It is slightly too terse for the ambiguity it leaves around null handling.

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 not be explained further, and that box is ticked. For a five-parameter mutation with no schema descriptions, though, the description should resolve the partial-update/null semantics, which is the largest remaining risk before invoking it.

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?

With 0% schema description coverage, the description must compensate and it only partly does: it names name, description, teacher and institution, covering four of five properties. It omits course_id's role as the required key and, more importantly, gives no meaning for the null defaults (clear vs. leave unchanged).

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?

Uses a specific verb ("Cambia") plus the resource ("curso") and enumerates the four mutable fields, with an "(Admin)" scope prefix. It is clearly distinguishable from update_question/update_user by resource name, though it does not explicitly contrast with them.

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 "(Admin)" marker implies a privilege precondition, which is useful context for when the tool is callable. However, there is no statement of when to use update_course vs create_course/delete_course, and no exclusions or preconditions beyond the admin tag.

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