Skip to main content
Glama

Delete a decision

delete_decision
DestructiveIdempotent

Permanently delete a decision and all its responses. The share link stops working. This cannot be undone, so confirm with the user first. Requires the admin_token.

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": {
      "decision_id": "<decision_id>",
      "admin_token": "<admin_token>"
    },
    "name": "delete_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
admin_tokenYesThe admin_token returned by create_decision.
decision_idYesDecision id or SettleIt link, e.g. "AbC123xYz9" or "https://settleit.now/p/AbC123xYz9".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description goes well beyond them by disclosing the concrete consequences: responses are deleted too, the share link stops working, and the action is irreversible. It also surfaces the auth requirement (admin_token), which is the kind of context annotations cannot carry.

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, with the destructive consequence and irreversibility front-loaded before the confirmation instruction. Every sentence carries distinct information (scope, side effect, reversibility, auth) with no 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 two-parameter destructive mutation with full schema coverage and rich annotations, the description covers consequences, auth, and the safety protocol. The only minor gap is that it does not indicate what a successful call returns or how errors surface, which is low-stakes since no output schema exists.

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%, so both parameters are already documented in the schema, including the link-or-id format for decision_id. The description only restates that admin_token is required, adding no new meaning; the baseline of 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 uses a specific verb and resource ("Permanently delete a decision") and clarifies the scope includes "all its responses", which distinguishes it from a soft-close. It does not explicitly name close_decision as the non-destructive alternative among the siblings, so the differentiation is implicit rather than stated.

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 provides a clear procedural guardrail ("confirm with the user first") and a prerequisite ("Requires the admin_token"), which gives usable context. However, it never says when to choose delete_decision over close_decision or reopen_decision, leaving the agent to infer that deletion is the irreversible path.

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