Skip to main content
Glama
soil-dev

capsulemcp

by soil-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_entry

Destructive

Permanently delete an entry by ID after setting confirm=true. Irreversible action removes notes, emails, or task records from Capsule CRM; repeated attempts report the entry as already deleted.

Instructions

DESTRUCTIVE & IRREVERSIBLE: permanently delete a note (or other entry) by its ID. Requires confirm=true. Idempotent on retry: response is {deleted: true, alreadyDeleted: false, id} on a fresh delete or {deleted: true, alreadyDeleted: true, id} if the entry was already gone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesEntry (note/email/task-record) ID
confirmYesMust be set to true. Permanently deletes the entry — use this to remove a note from a party/opportunity/project. Irreversible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • changedInput schema / required
      Previous value: -[
-  "confirm"
-]New value: +[
+  "id",
+  "confirm"
+]
  2. Addedv1.7.0
  3. Removedv1.6.2
  4. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

The description goes well beyond the destructiveHint annotation by explicitly stating that deletion is irreversible, requires confirm=true, and is idempotent on retry. It even discloses the exact two response variants, so the agent knows what to expect whether the entry existed or was already gone.

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 dense and economical: the warning is front-loaded, the precondition is stated in one short sentence, and the idempotency behavior is summarized with concrete response examples. Every sentence earns its place.

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 delete tool with no output schema, the description is unusually complete: it covers what happens on success, what happens when the entry is already deleted, and the required confirmation flag. No critical operational detail 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%, so the schema already documents both id and confirm. The description reinforces confirm's role but adds no parameter-level meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 names a specific verb ('permanently delete'), a specific resource ('a note (or other entry)'), and the means ('by its ID'). This clearly differentiates it from sibling delete tools like delete_party, delete_project, or delete_task by scoping it to entries.

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 gives clear context: this is the destructive deletion tool for entries and requires confirm=true as a precondition. It does not explicitly compare itself to sibling tools, but the entry scope and confirm requirement provide enough guidance for correct selection.

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