Skip to main content
Glama

delete_habit

Destructive

Delete a routine. Prefer update_habit with active false to pause it.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is supplied structurally. The description adds the useful contextual point that a reversible pause exists and is preferred, which frames deletion as the heavier option. It does not say whether the delete is permanent, whether history is retained, or whether confirmation is required, so it adds only modest value beyond the annotations.

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 with zero filler, and the destructive action is stated first with the safer alternative immediately after. Nothing is padded or restated.

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

Completeness3/5

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

The tool is simple and the annotations carry the destructive flag, so a short description is defensible, and the pause alternative is a genuinely valuable addition. However, with an undocumented required id and no output schema, the definition leaves the agent guessing about the identifier it must supply and about the permanence of the deletion.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single required id parameter, so the description carries the full burden of explaining it and says nothing. It does not clarify whether id is a habit identifier, where to obtain it, or what format it takes; the agent must infer this from the tool name alone.

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?

"Delete a routine" gives a specific verb and resource, and the follow-up sentence names the sibling tool that offers a non-destructive path, so an agent can place it relative to update_habit. The wording "routine" rather than "habit" is a minor inconsistency with the tool name and the sibling set, but intent is still unambiguous.

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?

The description explicitly routes the agent: if the goal is to pause rather than remove, use update_habit with active false. That is a concrete alternative plus the condition that selects it. It stops short of stating when deletion is actually appropriate (e.g. only on explicit user request), so it is clear but not exhaustive.

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