Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Quitar a alguien del aula

remove_member
Destructive

Removes a person from a classroom and revokes their access; requires explicit confirmation because the action cannot be undone.

Instructions

[Equipo del aula · irreversible] Quita la plaza de una persona del aula. Pierde el acceso. Pide confirmación explícita a la persona.

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>",
      "member_id": "<member_id>",
      "confirm": "<confirm>"
    },
    "name": "remove_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesDebe ser true: la persona confirmó esta acción irreversible
member_idYesPlaza
classroom_idYesAula

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds substantive context beyond them: the action is 'irreversible' and the person 'pierde el acceso'. Requiring explicit human confirmation is real behavioral guidance an agent needs before invoking a destructive call.

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?

Three short clauses with the scope and irreversibility front-loaded in the bracketed tag. Every sentence carries information and nothing is redundant.

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 3-parameter destructive mutation with full annotations and schema coverage, the definition covers consequences, irreversibility and the confirmation requirement. The only gap is that no return/outcome behavior is described, though no output schema exists to compensate.

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% and both ID parameters are documented as 'Plaza' and 'Aula' in the schema. The description reinforces that confirmation must come from the person being removed, but adds no format or constraint detail beyond what the schema already carries, so the baseline 3 applies.

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: 'Quita la plaza de una persona del aula' (removes a person's seat from the classroom). That clearly separates it from read/listing siblings like list_members. It stops short of naming adjacent operations such as decide_access_request or set_course_grants, so it is clear but not fully sibling-differentiated.

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?

It gives a procedural precondition ('Pide confirmación explícita a la persona') and the scope tag 'Equipo del aula', implying this is used when removing a member from the classroom team. It never states when not to use it or points to an alternative tool, so usage is only implied.

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