Skip to main content
Glama

Delete a loop

delete_loop
DestructiveIdempotent

Delete a loop for good (its tasks are kept). Cannot be undone: confirm with the user first.

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": {
      "loop_id": "<loop_id>"
    },
    "name": "delete_loop"
  }
}

Input Schema

NameRequiredDescriptionDefault
loop_idYesThe loop's id (from list_loops).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description earns credit for disclosing what the annotations cannot: the delete is permanent and non-cascading — associated tasks survive. It still says nothing about the response, permission requirements, or behavior when the loop is missing.

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 tight sentences, with the scope fact front-loaded before the irreversible-action warning. Nothing is redundant or padded.

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 one-parameter destructive tool with rich annotations and no output schema, the definition covers the essentials: what is removed, what is preserved, and the confirmation requirement. Only return/error behavior is left unstated, which is a minor gap given the annotation coverage.

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?

There is a single required parameter with 100% schema description coverage; the schema already explains that loop_id comes from list_loops. The description adds no further meaning about the id, so the baseline of 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?

States a specific verb and resource ('Delete a loop') and immediately adds a distinguishing scope detail — 'its tasks are kept' — that separates it from delete_task, which would remove the tasks themselves. An agent can tell the two siblings apart without opening either schema.

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 an explicit usage precondition: 'confirm with the user first' before invoking, tied to irreversibility. It does not name an alternative path (e.g., update_loop or a soft-disable) or state when-not to use it, so it falls short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources