Skip to main content
Glama

rr_dismiss_recommendation

Destructive

Dismiss a recommendation when no buyer action is needed, record the dismissal reason, and remove it from active action queues.

Instructions

Dismiss a recommendation when the seller decides no buyer work is needed. Records an action event and removes it from active action queues.

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>"
    },
    "name": "rr_dismiss_recommendation"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional dismissal reason.
action_idYesRecommendation id (required).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the agent knows this is a non-idempotent mutation. The description does add genuine value beyond that by stating the two effects — an action event is recorded and the item leaves active action queues — which explains why the operation is destructive. However, it says nothing about reversibility, whether the rationale is preserved for audit, or what the caller gets back.

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 sentences, no filler, and the trigger condition is front-loaded before the side effects. Every clause earns its place.

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?

With only two parameters, full schema coverage, and annotations carrying the safety profile, the definition is nearly complete. The remaining gap is that an agent cannot tell from this text how dismissal differs from closing the same recommendation, which matters for correct tool selection.

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 description coverage is 100%, so both parameters (action_id, reason) are already documented in the schema, and the description adds no syntax, format, or constraint detail beyond that. A 3 baseline is appropriate here; nothing is added, but nothing needed is missing.

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 ('Dismiss a recommendation') and adds the decision context that triggers it ('seller decides no buyer work is needed'). It is clear on its own, but it never distinguishes itself from the near-identical sibling rr_close_recommendation, so an agent must infer which of the two terminal actions applies.

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?

It gives a real usage condition: call this when the seller judges that no buyer work is required. That is clear context rather than a bare restatement of the name. It stops short of any exclusion or alternative routing (e.g. close vs dismiss), which is what would be needed for a 5.

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