Skip to main content
Glama

Delete a deal

delete_deal
Destructive

Permanently remove one deal (a card on the pipeline board). This permanently deletes data and cannot be undone. Only the deal goes: the lead it came from, the linked contact and their timeline are kept. Use it for a duplicate or junk card. If the deal simply did not close, move_deal_stage into a Lost stage instead, which keeps the record. Get deal ids from list_opportunities. Call without confirm to see what would be removed.

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": {
      "opportunity_id": "<opportunity_id>"
    },
    "name": "delete_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually perform this. Call once WITHOUT it to receive a summary of exactly what will be destroyed, show that summary to the user, and only then call again with true.
opportunity_idYesThe deal id, as returned by list_opportunities

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/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 known; the description goes further by disclosing the exact blast radius ('Only the deal goes: the lead it came from, the linked contact and their timeline are kept') and the irreversibility ('cannot be undone'). It also surfaces the two-step preview behavior, which is the practical mechanic an agent must follow before mutating.

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?

Five short sentences, front-loaded with the permanence warning, then scope, then the alternative, then the id source, then the preview step. No filler or hedging; each sentence adds a distinct decision-relevant fact.

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 two-parameter mutation tool with no output schema, the description covers what an agent needs: irreversibility, non-cascading retention, the safer alternative, id provenance, and the confirmation flow. Nothing material is left for the caller to infer.

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%, with the confirm parameter's dry-run protocol fully documented in the schema itself, so the description's mention of 'Call without confirm to see what would be removed' is largely restatement. The opportunity_id provenance note duplicates the schema description of that field. Baseline 3 applies because the schema already carries the semantics.

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?

States a specific verb and resource ('Permanently remove one deal'), parenthetically defines the domain object ('a card on the pipeline board'), and implicitly separates itself from delete_contact/delete_pipeline by scoping to a single deal. An agent can distinguish this from move_deal_stage and the other delete_* siblings without opening a schema.

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?

Gives explicit when-to-use ('duplicate or junk card') and when-not-to-use with a named alternative ('If the deal simply did not close, move_deal_stage into a Lost stage instead, which keeps the record'). It also names list_opportunities as the id source, so the whole call path is resolved.

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