Skip to main content
Glama

Delete Tag

delete_tag
Destructive

Deletes a tag after confirmation. Set remove_associations to true to detach linked students and courses first and return the list for recovery.

Instructions

(Admin) Borra una tag. Pide confirmación.

La API solo borra tags sin alumnos ni cursos. Con remove_associations=true primero los desasocia (los alumnos pierden el acceso que les daba esa tag) y devuelve la lista para poder rehacerlo.

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": {
      "tag_id": "<tag_id>"
    },
    "name": "delete_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
tag_idYes
confirm_tokenNo
remove_associationsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds substantial context on top: admin privilege required, a confirmation step, the API's refusal condition, and the real consequence that students lose access granted through the tag. It even notes the call returns the detached list so the change can be rebuilt — exactly the operational detail an agent needs before a destructive write.

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?

Four short sentences, front-loaded with the action and the admin/confirmation constraint, then the API restriction, then the remove_associations escape hatch. Nothing is repeated and no sentence is filler.

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 destructive, non-idempotent tool the safety picture, prerequisites, and association side effects are all covered, and an output schema exists so return values need no explanation. The remaining gap is the confirm_token lifecycle, which an agent must understand to complete the call successfully.

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 carries the burden and does well for remove_associations, spelling out its side effects. However, confirm_token is only hinted at by "Pide confirmación" — it never says how the token is obtained or what an invalid token does — and tag_id is left self-evident.

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?

States a specific verb and resource ("Borra una tag") plus an admin-only scope marker, which separates it from siblings like remove_students_from_tag or unlink_tag_to_course that also touch tags. It does not explicitly name the sibling to use instead when only an association needs removing, but the destructive intent is unmistakable.

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?

Gives a concrete precondition (the API only deletes tags with no students or courses) and the fallback path: set remove_associations=true to detach first. That is genuine when/when-not guidance tied to the tool's behavior, though it never routes to a named alternative tool for the association-removal case.

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