Skip to main content
Glama

rr_create_draft_from_recommendation

DestructiveIdempotent

Convert a recommendation into a draft purchase order or transfer for human review. Nothing is sent and no stock moves; supply the action’s last-read updated_at to prevent stale changes.

Instructions

Turn a recommendation into its draft purchase order or draft transfer, for a person to review. Nothing is sent to a supplier and no stock moves. It needs the action's updated_at as last read; if the user has not given it, read it with rr_preview_recommendation.

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": {
      "action_id": "<action_id>",
      "idempotency_key": "<idempotency_key>",
      "expected_updated_at": "<expected_updated_at>"
    },
    "name": "rr_create_draft_from_recommendation"
  }
}

Input Schema

NameRequiredDescriptionDefault
action_idYesThe recommendation id, from rr_list_recommendations.
idempotency_keyYesA value you choose for this attempt. Repeating a call with the same value and the same arguments returns the first result and does nothing again.
expected_updated_atYesThe action's updated_at as last read (rr_preview_recommendation or rr_get_recommendation). The call is refused if the action changed since, so it can be read again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare this as a write operation with idempotency and conservative safety flags. The description adds important operational context: it creates a draft for human review, sends nothing to a supplier, moves no stock, and refuses the call if the recommendation changed since expected_updated_at was read.

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 with no wasted wording. Purpose, safety boundary, and prerequisite are front-loaded and easy to scan.

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

Completeness4/5

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

For a mutation tool with no output schema, the description covers the critical call behavior: what gets created, that it is only a draft, that no supplier or stock action occurs, and how to handle stale state. It could mention return expectations or the retry sibling, but the essential invocation context is present.

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%, and the schema already explains action_id, idempotency_key, and expected_updated_at in detail. The description mainly restates the stale-read check and adds the practical fallback of reading with rr_preview_recommendation when the user has not provided updated_at, which is useful but limited beyond the schema.

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: turning a recommendation into its draft purchase order or draft transfer. It also distinguishes the result from a real order by saying it is for human review, nothing is sent to a supplier, and no stock moves.

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 use case is clear: create the draft version of a recommendation for review. It also gives an explicit prerequisite alternative, rr_preview_recommendation, when the user has not supplied updated_at, though it does not state when to avoid this tool in favor of retry or direct purchase-order creation.

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