Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Transferir curso

transfer_course
Destructive

Transfers course ownership to another teacher; only the course creator can initiate it and must confirm the irreversible change first.

Instructions

[Equipo del aula · irreversible] Transfiere la propiedad de un curso a otro docente. Solo quien lo creó. Pide confirmación explícita antes de hacerlo.

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": {
      "classroom_id": "<classroom_id>",
      "course_id": "<course_id>",
      "new_owner_id": "<new_owner_id>",
      "confirm": "<confirm>"
    },
    "name": "transfer_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesDebe ser true: la persona confirmó esta acción irreversible
course_idYesCurso
classroom_idYesAula
new_owner_idYesDocente de destino

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false. The description goes beyond them by naming the effect (ownership passes to another teacher), stating that the action is irreversible, and restricting who may invoke it. It does not say what happens to the previous owner's access or which errors can occur.

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?

The bracket tag puts the destructive and irreversible nature first, followed by purpose, authorization, and the confirmation rule. Every sentence adds information, and there is no redundant wording.

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

Completeness4/5

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

For a four-required-parameter mutation with no output schema, the description covers purpose, permission, irreversibility, and the confirmation gate. The remaining gap is failure behavior, such as what happens if the target teacher is not a member of the classroom.

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 100%, so the schema already labels each of the four parameters, including the required confirm=true flag. The description adds no syntax or format detail beyond what the schema provides, so the baseline of 3 is appropriate.

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: transferring ownership of a course to another teacher. This action is unique among the siblings, so no sibling overlap exists. Differentiation is implicit rather than named, which keeps it short of a 5.

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 a clear authorization condition (only the person who created it) and a workflow prerequisite (ask for explicit confirmation before proceeding). It does not name alternatives such as update_course or delete_course, but none of them would be mistaken for this operation.

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

Deploy Server

Other Tools