Skip to main content
Glama

send_draft

Sends a pending negotiation draft only after the buyer has seen that exact text and clearly agreed; any edited message requires a new draft and fresh confirmation.

Instructions

Send the pending draft of a negotiation. Call this only after the buyer has seen exactly this draft and clearly said yes. A changed text needs a new draft_message and a new yes.

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": "send_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

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does real work by disclosing a hard state precondition: the draft must be unchanged and verbally confirmed. It leaves gaps on post-send behavior, such as whether the draft is consumed, whether the send is reversible, and what the response contains.

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 short sentences, imperative first, with the confirmation rule front-loaded and the invalidation rule following it. Every sentence adds a distinct constraint; nothing is padding.

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

Completeness3/5

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

For a consequential send action with no annotations and no output schema, the definition covers the safety precondition well but says nothing about what sending does to the draft or negotiation state afterward. An agent can decide whether to call it, but not what to expect from the call.

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 one parameter with 100% schema coverage; the schema already explains negotiation_id and its provenance (start_negotiation / list_negotiations). The description adds no further meaning to the parameter, 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?

States a specific verb and resource: sending the pending draft of a negotiation. That distinguishes it from draft_message (which creates the draft) and discard_draft. It stops short of explicitly naming a sibling, so the differentiation is inferable rather than stated.

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 an explicit precondition (the buyer has seen exactly this draft and clearly said yes) and an explicit when-not plus alternative: changed text requires a new draft_message and a new yes. That is exactly the routing information an agent needs before committing.

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