Skip to main content
Glama

Submit feedback

submit_feedback

Report observations that could help improve Rainbrand: bugs or errors, surprises, limitations, workflow friction, misleading documentation, missing capabilities, or disappointing or degraded results. You do not need to establish the root cause when the observation concerns Rainbrand. Report each distinct issue once. Do not report failures wholly unrelated to Rainbrand. Leave out credentials, personal or customer data, transcripts, source files, private prompts, and unrelated task context. Reports are internal product feedback and do not open a support conversation. Continue the original task whether submission succeeds or fails.

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

Input Schema

NameRequiredDescriptionDefault
messageYesWhat Rainbrand did, what you expected, and the effect on the task. Omit private task content.
categoryNoClassify what went wrong: incorrect behavior, misleading documentation, workflow friction, a missing capability, or disappointing results. Use other when none fits.other
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
tool_nameNoName of the Rainbrand tool involved, if known.
related_idNoRainbrand-generated ID of the affected resource or operation, such as a Brand or generation ID, if known.

Output Schema

NameRequiredDescriptionDefault
statusYes
message_for_assistantYesGuidance for continuing after the feedback submission.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare it is not read-only, not destructive, not idempotent, and closed-world; the description adds real context beyond that: reports are internal product feedback rather than a support conversation, no root-cause analysis is required, and the caller should proceed with the original task whether or not submission succeeds (fire-and-forget semantics). It stops short of saying where reports land or whether they are anonymous, which keeps it from a 5.

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?

The scope statement is front-loaded and each subsequent sentence covers a distinct rule (dedupe, out-of-scope, redaction, non-support, keep working). The enumeration of issue types is long but functional; the list could be trimmed slightly without loss.

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

Completeness5/5

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

An output schema exists and annotations cover the safety profile, so the description only needs to cover intent, scope, privacy, and post-call behavior — and it does all four. An agent knows exactly what to submit, what to omit, and what to do next.

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 message, category enum, llm_model, tool_name, and related_id are all already documented — baseline 3 applies. The description adds privacy constraints on message content (no credentials, personal or customer data, transcripts, source files, private prompts), but that partially overlaps the schema's own 'Omit private task content' note and adds nothing about category or related_id.

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?

Names a specific verb (report) and a specific resource (observations that could improve Rainbrand), then enumerates the accepted issue classes: bugs, surprises, limitations, workflow friction, docs mismatch, missing capabilities, quality degradation. This is unambiguously a product-feedback channel and cannot be confused with any sibling such as create_review or get_generation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit positive triggers (report observations needing no root cause), explicit exclusions (do not report failures wholly unrelated to Rainbrand), a deduplication rule (report each distinct issue once), and a post-call instruction (continue the original task regardless of outcome). Alternatives are not needed here because no sibling performs this function.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources