Skip to main content
Glama
Sign In
Chispa MCP

Chispa MCP

by jeffercbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Borrar oferta

delete_offer
Destructive

Permanently deletes an offer from a classroom after explicit confirmation; use when an offer must be removed irreversibly.

Instructions

[Administrador del aula · irreversible] Borra una oferta del aula. Irreversible: 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>",
      "offer_id": "<offer_id>",
      "confirm": "<confirm>"
    },
    "name": "delete_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesDebe ser true: la persona confirmó
offer_idYesOferta
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 declare destructiveHint=true and readOnlyHint=false, but the description adds real context beyond them: the required administrator role, the irreversibility, and the obligation to obtain explicit human confirmation before calling. It still does not say what happens to dependent data (enrollments, sales) when the offer is removed.

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, front-loaded with a bracketed role/risk tag followed by the action and the safety constraint. Every clause carries information an agent needs; nothing is padding.

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 three-parameter destructive tool with full schema coverage and no output schema, the description covers the essentials: what is deleted, the permission level, the irreversibility, and the confirmation duty. It is slightly thin on downstream effects of deletion, which matters for a destructive operation.

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 each of the three parameters carries its own description, including the const-true confirm flag, so the schema does the heavy lifting. The description only gestures at the confirmation requirement and adds no format or identifier semantics beyond that, which is the baseline case.

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 ("Borra una oferta del aula"), making the operation unambiguous. It does not explicitly contrast with the nearby siblings set_offer_active or update_offer, so an agent must infer that this permanently removes the offer rather than toggling its state.

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?

Usage is implied rather than stated: deletion of a classroom offer. There is no guidance on when to prefer this over set_offer_active (deactivation) or update_offer, which is the most likely confusion given those siblings. The permission prerequisite (classroom administrator) is a useful hint but not a when-to-use rule.

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