Skip to main content
Glama

rr_add_recommendation_note

Add seller context notes directly to a recommendation so important details stay with the recommendation instead of a purchase order.

Instructions

Add a note to a recommendation: context the seller wants kept on the recommendation itself rather than on a purchase order.

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

Input Schema

NameRequiredDescriptionDefault
noteYesNote body (required).
action_idYesRecommendation id (required).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the note persists on the recommendation object itself, but says nothing about whether notes append or replace, who can see them, or any length/rate limits.

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?

A single front-loaded sentence with the verb and resource first and the disambiguating scope trailing. The clause after the colon is slightly wordy but earns its place by separating it from the purchase-order note sibling.

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 simple two-parameter, non-destructive write with full schema coverage and declared annotations, the description supplies enough purpose and placement context. Return behavior is unspecified, but with no output schema and a trivially understood operation, that gap is minor.

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 the note body and the recommendation id are documented in the schema. The description clarifies the note's intended semantic content ('context the seller wants kept') but adds no format or length details beyond the schema; 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?

Names a specific verb and resource ('Add a note to a recommendation') and adds scope, distinguishing it from the sibling rr_add_purchase_order_note by contrasting where the note lives.

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?

Usage is implied through the contrast with purchase-order notes, which points an agent toward this tool when the context belongs to the recommendation. However, there is no explicit statement of when not to use it or of prerequisites (e.g., whether the recommendation must be open).

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