Skip to main content
Glama

rr_submit_feedback

Submit user-approved bug, suggestion, or support feedback to ReplenishRadar with needed context and no extra personal/store data; duplicate messages return the first report.

Instructions

Sends feedback the user has agreed to pass on to the ReplenishRadar product team, on the user's behalf. The report says what the user wanted and what happened, with no names, contact details, credentials, or store data beyond what the report needs. Sending the same message twice returns the first report and files no second one.

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": {
      "type": "<type>",
      "message": "<message>"
    },
    "name": "rr_submit_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesbug: something is broken or wrong. suggestion: something the user wishes ReplenishRadar did. support: the user needs help. other: anything else.
impactNoOptional: how much this is holding the user back.
messageYesWhat the user was trying to do, what happened, and what they expected.
subjectNoOptional one-line summary.
related_toolNoOptional: the ReplenishRadar tool the feedback is about, by name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

A3.7/5.0
Behavior2/5

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

The description adds genuinely useful behavior beyond the annotations: data minimization (no names, contact details, credentials, or surplus store data) and an explicit dedupe rule where a repeated message returns the first report and files nothing new. However, that dedupe promise ('files no second one') describes idempotent behavior while the annotations declare idempotentHint=false, which is a direct conflict. The valuable privacy disclosure keeps this above the minimum, but the inconsistency is material.

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?

Three sentences that are front-loaded with the purpose, then the content/privacy constraint, then the duplicate-send behavior. Every sentence carries information, though the middle sentence is a dense list that takes a second pass to parse cleanly.

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 five parameters, no output schema, and no nested objects, the description covers purpose, consent, content restrictions, and repeat-call behavior. The remaining gap is the return value: it mentions a 'report' being returned but never says what that report contains, and there is no output schema to fall back on.

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% and every parameter (type, impact, message, subject, related_tool) carries its own enum values and constraints, so the baseline is 3. The description only reinforces content semantics — 'what the user wanted and what happened' — and adds a privacy constraint on what may go in the message, without elaborating any specific field.

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?

States a specific verb and resource: sends user-consented feedback to the ReplenishRadar product team on the user's behalf. No sibling tool in the catalog deals with feedback, and the description makes the resource and direction of flow unmistakable without opening the schema.

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?

Gives a clear triggering condition — the user has agreed to pass the feedback on — which functions as a consent gate an agent can act on. It stops short of naming when not to use it (e.g., local-only issues, or routing to support tooling instead) or any alternative path, so it is clear context rather than full routing guidance.

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