Skip to main content
Glama
Sign In
CarryMem

CarryMem

by lulin70
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_rule

Remove a memory rule by its ID. Use my_rules to find the ID, then permanently erase it. Returns confirmation with the deleted rule's details.

Instructions

Delete a rule by its ID. Use my_rules first to find the rule ID you want to remove. Returns confirmation with the deleted rule's details.

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": {
      "rule_id": "<rule_id>"
    },
    "name": "delete_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
rule_idYesThe ID of the rule to delete (find it using my_rules)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses that the tool returns confirmation with deleted rule details, which is sufficient for a simple destructive action. Lacks mention of irreversibility, but that is implied by 'delete'.

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 concise sentences, zero waste. Each sentence earns its place: first states the action, second gives prerequisite and return info.

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 single-parameter delete tool with no output schema, the description completely covers the purpose, prerequisite, and return behavior. No gaps.

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 coverage is 100%, so the description adds little beyond what the schema already provides. It repeats 'find it using my_rules' from the schema description, offering no new semantic detail.

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 explicitly states 'Delete a rule by its ID', using a specific verb and resource. It clearly distinguishes the tool's action from siblings like add_rule or update_rule.

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?

Provides explicit guidance to use my_rules first to find the rule ID, which is a helpful prerequisite. No need for when-not-to-use given the simplicity of a delete operation.

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