Skip to main content
Glama

rr_close_recommendation

DestructiveIdempotent

Closes a replenishment recommendation with a reason when no purchase order or transfer is needed, removing it from open lists without creating anything.

Instructions

Close a recommendation with a reason when no purchase order or transfer is needed, for example because the stock was bought another way. Removes it from the open lists and creates nothing.

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>",
      "reason": "<reason>",
      "idempotency_key": "<idempotency_key>",
      "expected_updated_at": "<expected_updated_at>"
    },
    "name": "rr_close_recommendation"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy no purchase order or transfer is needed.
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

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real substance: the record disappears from open lists and no downstream artifact is created. That clarifies the destructive impact is limited to list visibility rather than a created entity, and it explains why the reason parameter matters. It does not state whether the close can be reversed or reopened.

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?

Two short sentences, no filler: the first states the action plus its qualifying condition, the second states the observable effect. The consequence clause is front-loaded where the agent needs it.

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 four-required-parameter mutation with no output schema and full annotation coverage, the description covers what the tool does, when it applies, and its side effect on open lists. The remaining gap is reversibility and the close-vs-dismiss distinction, which are not addressed anywhere in the definition.

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 every parameter carries a substantive description, including the idempotency and optimistic-concurrency semantics of expected_updated_at. The prose adds no parameter meaning beyond naming the required reason, so the baseline 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?

The description names a specific verb and resource ('Close a recommendation') and pins down the triggering condition ('when no purchase order or transfer is needed'), with a concrete example. It implies a contrast with drafting/ordering paths, but never names a sibling such as rr_dismiss_recommendation or rr_create_draft_from_recommendation, so the boundary between close and dismiss must be inferred.

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 description gives a clear positive condition for use ('no purchase order or transfer is needed') and an example case. It gives no when-not guidance and does not route the agent to the obvious alternatives (dismiss vs. create a draft), which is the main decision an agent faces with this family of tools.

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