Skip to main content
Glama
soil-dev

capsulemcp

by soil-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_opportunity

Destructive

Permanently delete an opportunity from Capsule CRM. Confirm with confirm=true to prevent accidental irreversible deletion.

Instructions

DESTRUCTIVE & IRREVERSIBLE: permanently delete an opportunity. Requires confirm=true. Always read the opportunity first with get_opportunity and confirm with the user before calling. Idempotent on retry: response is {deleted: true, alreadyDeleted: false, id} on a fresh delete or {deleted: true, alreadyDeleted: true, id} if the opportunity was already gone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
confirmYesMust be set to true. Permanently deletes the opportunity. 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.7/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description adds irreversibility, the confirm=true requirement, retry idempotency, and the exact response shape for both fresh deletes and already-deleted cases. This is rich behavioral context that the annotations alone do not provide.

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?

Three compact sentences: the destructive warning is front-loaded, followed by required preconditions, and then retry behavior. Every sentence earns its place with no filler or repetition.

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 two-parameter tool with no output schema, the description provides the essential workflow, confirmation requirement, return values, and idempotent retry behavior. Nothing critical is missing for an agent to call it correctly.

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?

The schema already documents confirm well. The description reinforces confirm=true and implies id targets an opportunity, but it does not add substantial new meaning for id beyond what the schema's name and constraints convey. Schema coverage is 50%, so this is adequate but not exceptional.

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 states a specific verb and resource: 'permanently delete an opportunity.' It is immediately distinguishable from read tools like get_opportunity, update_opportunity, and list_deleted_opportunities, and it emphasizes the destructive nature clearly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit preconditions: read the opportunity first with get_opportunity, confirm with the user, and set confirm=true. It clearly tells the agent when and how to invoke the tool safely, including the required confirmation step.

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