Skip to main content
Glama
Sign In
utn-mcp

utn-mcp

by nialvape
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

aula_forum_delete_post

DestructiveIdempotent

Permanently deletes your own forum post after confirmation when deletion is permitted; deleting a discussion's first post removes the whole discussion.

Instructions

Borra una publicación propia de un foro. No se puede deshacer. Solo se puede si tiene "borrar" en acciones. Si es la primera publicación de la discusión, se borra la discusión entera.

Antes de llamarla, mostrale al usuario exactamente lo que se va a hacer y esperá que confirme.

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": {
      "direccion": "<direccion>",
      "id": "<id>"
    },
    "name": "aula_forum_delete_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes`id` de la publicación, de aula_open. Ej: 768118.
direccionYesDirección de la discusión donde está la publicación. Ej: "/curso/691/mod/34831/disc/416676".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.3

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare `destructiveHint=true`, but the description adds essential context beyond them: deletion cannot be undone, it is gated on `borrar` in `acciones`, and deleting the first post removes the entire discussion. It also requires showing the user exactly what will happen and waiting for confirmation.

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 description is tightly written: destructive action and irreversibility are front-loaded, followed by the permission gate, cascade risk, and confirmation instruction. No sentence is filler or redundant.

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

Completeness5/5

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

For a destructive mutation with no output schema, the description covers the key operational facts: irreversibility, permission gating, cascading deletion of the whole discussion, and required user confirmation. Nothing critical to safe invocation is missing.

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` and `direccion` are fully documented with examples in the schema. The description adds only indirect scoping through 'publicación propia' and does not define parameter formats beyond what the schema already provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Borra') and resource ('una publicación propia de un foro'), with the ownership scope making the operation distinct from creating or editing posts. The cascade note further clarifies exactly what kind of deletion this is.

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 states a clear precondition ('Solo se puede si tiene "borrar" en `acciones`') and mandates a confirmation workflow before calling, which tells the agent when the tool is allowed to be used. It does not explicitly compare with alternatives such as `aula_forum_edit_post`, so it stops short of a 5.

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