Skip to main content
Glama

discard_draft

Deletes a pending negotiation draft without sending it, letting you cancel an unsent message and keep the conversation unchanged.

Instructions

Drop the pending draft of a negotiation without sending 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": {
      "negotiation_id": "<negotiation_id>"
    },
    "name": "discard_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
negotiation_idYesNegotiation id from start_negotiation / list_negotiations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that nothing is sent, but says nothing about whether the draft is permanently deleted, whether the action is reversible, whether it errors when no draft exists, or what permissions are needed for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single tight sentence that front-loads the action and its key constraint. Nothing is wasted, though there is little structure beyond that one clause.

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

Completeness2/5

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

For a tool that discards pending work, with no annotations and no output schema, the definition should at least state irretrievability and error behavior. As written, an agent cannot tell whether calling this destroys recoverable state or how to handle a missing draft.

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?

There is only one parameter and schema coverage is 100%: the schema already says the negotiation_id comes from start_negotiation / list_negotiations. The description adds no further meaning about the identifier, so the baseline of 3 applies.

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?

"Drop the pending draft of a negotiation" states a specific verb and resource, and "without sending it" implicitly contrasts with the send_draft sibling. It stops short of naming the alternative explicitly, but an agent can still distinguish the operation.

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

Usage Guidelines3/5

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

The phrase "without sending it" hints that this is the alternative to send_draft, so the usage is implied rather than stated. There is no explicit "use this when you want to abandon a draft instead of sending it," and no mention of prerequisites such as an existing pending draft.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.