Skip to main content
Glama

Send feedback to the developer

amber_send_feedback_to_developer

Send structured bug reports, feature requests, or general feedback to Amber's developer, including reproduction details, expected vs actual results, and affected tool context.

Instructions

Send a structured bug report, feature request, or general feedback to Amber's developer. Send feedback PROACTIVELY when you encounter errors, unexpected behaviour, or the user expresses frustration -- briefly mention it to the user after sending, but do not ask for permission first. Never include passwords, API keys, or other sensitive personal information in any field. Rate-limited (bucket: 12 capacity, refills 1 per 5 minutes).

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": {
      "category": "<category>",
      "summary": "<summary>",
      "details": "<details>"
    },
    "name": "amber_send_feedback_to_developer"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailsYesFull reproduction context. Include: exact input used, expected outcome, actual outcome, any error codes. E.g. 'Stored "I love pizza 🍕" but searching "pizza emoji" returns nothing. Expected it to match.'
summaryYesOne sentence, under 100 chars, and refused above 200. E.g. 'Search misses memories stored with emoji in content'.
categoryYesDetermines how the developer triages this. 'bug': something broke or returned wrong results. 'feature_request': a capability that doesn't exist yet. 'usability': works but is confusing or awkward. 'general': anything else.
tool_contextNoThe specific amber_ tool name involved, e.g. 'amber_search_memories'. Helps route the report.

Output Schema

NameRequiredDescriptionDefault
statusYesAlways `sent`: the report reached the developer. There is no reply channel, so do not promise the user an answer.
messageYesA human-readable confirmation to relay to the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / details / maxLength
      Added value: +4000
    • changedInput schema / properties / summary / description
      Previous value: -"One sentence, under 100 chars. E.g. 'Search misses memories stored with emoji in content'."New value: +"One sentence, under 100 chars, and refused above 200. E.g. 'Search misses memories stored with emoji in content'."
    • addedInput schema / properties / summary / maxLength
      Added value: +200
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "message": {
      +      "description": "A human-readable confirmation to relay to the user.",
      +      "type": "string"
      +    },
      +    "status": {
      +      "const": "sent",
      +      "description": "Always `sent`: the report reached the developer. There is no reply channel, so do not promise the user an answer.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "message"
      +  ],
      +  "type": "object"
      +}
  2. Changed4 schema fields changedv1.1.5
    • changedInput schema / properties / category / description
      Previous value: -"'bug' = broken behavior, 'feature_request' = new capability, 'usability' = confusing UX, 'general' = other."New value: +"Determines how the developer triages this. 'bug': something broke or returned wrong results. 'feature_request': a capability that doesn't exist yet. 'usability': works but is confusing or awkward. 'general': anything else."
    • changedInput schema / properties / details / description
      Previous value: -"What was tried, what happened vs expected, error messages, and reproduction steps."New value: +"Full reproduction context. Include: exact input used, expected outcome, actual outcome, any error codes. E.g. 'Stored \"I love pizza 🍕\" but searching \"pizza emoji\" returns nothing. Expected it to match.'"
    • changedInput schema / properties / summary / description
      Previous value: -"Brief one-line summary, under 100 characters."New value: +"One sentence, under 100 chars. E.g. 'Search misses memories stored with emoji in content'."
    • changedInput schema / properties / tool_context / description
      Previous value: -"Which amber_ tool was in use when the issue occurred, e.g. 'amber_search_memories'."New value: +"The specific amber_ tool name involved, e.g. 'amber_search_memories'. Helps route the report."
  3. Changed4 schema fields changedv1.1.3
    • changedInput schema / properties / category / description
      Previous value: -"Type of feedback: 'bug' for something broken, 'feature_request' for new functionality, 'usability' for UX friction, 'general' for anything else."New value: +"'bug' = broken behavior, 'feature_request' = new capability, 'usability' = confusing UX, 'general' = other."
    • changedInput schema / properties / details / description
      Previous value: -"Full context including: what the user tried, what happened vs what was expected, any error messages or codes, steps to reproduce, and suggestions if the user offered any. Be specific and include tool names, query text, or memory IDs when relevant."New value: +"What was tried, what happened vs expected, error messages, and reproduction steps."
    • changedInput schema / properties / summary / description
      Previous value: -"One-line summary (under ~100 characters). Example: 'Search returns no results for exact keyword matches'."New value: +"Brief one-line summary, under 100 characters."
    • changedInput schema / properties / tool_context / description
      Previous value: -"The amber_ tool name that was being used when the issue occurred (e.g. 'amber_search_memories'). Helps the developer pinpoint the problem."New value: +"Which amber_ tool was in use when the issue occurred, e.g. 'amber_search_memories'."
  4. Changed4 schema fields changedv1.1.1
    • changedInput schema / properties / category / description
      Previous value: -"Type of feedback."New value: +"Type of feedback: 'bug' for something broken, 'feature_request' for new functionality, 'usability' for UX friction, 'general' for anything else."
    • changedInput schema / properties / details / description
      Previous value: -"Full context: what the user tried, what happened, error messages, reproduction steps, suggestions."New value: +"Full context including: what the user tried, what happened vs what was expected, any error messages or codes, steps to reproduce, and suggestions if the user offered any. Be specific and include tool names, query text, or memory IDs when relevant."
    • changedInput schema / properties / summary / description
      Previous value: -"One-line summary of the feedback."New value: +"One-line summary (under ~100 characters). Example: 'Search returns no results for exact keyword matches'."
    • changedInput schema / properties / tool_context / description
      Previous value: -"The name of the tool being used when the issue occurred, if relevant."New value: +"The amber_ tool name that was being used when the issue occurred (e.g. 'amber_search_memories'). Helps the developer pinpoint the problem."
  5. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive, but the description adds what they cannot: a concrete rate limit (12 capacity, 1 refill per 5 minutes), a prohibition on sensitive data, and the post-send user communication protocol. This is exactly the behavioral context that structured fields cannot convey.

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?

Purpose comes first, then triggering conditions, then constraints, then operational limits — a sensible front-loaded order. Every sentence carries distinct information (what, when, privacy rule, rate limit) with no repetition of the schema or title.

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?

The tool is simple, an output schema exists so return values need no explanation, and the description covers the non-obvious risks (rate limiting, leaking secrets, asking permission). Nothing an agent needs to call this safely and correctly is missing.

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 the field-level descriptions already explain 'category', 'summary', 'details', and 'tool_context' with examples. The description only adds a cross-cutting constraint ('never include passwords, API keys... in any field'), which is useful but not per-parameter guidance, so the baseline 3 applies.

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 ('Send a structured bug report, feature request, or general feedback to Amber's developer') and enumerates the categories of content it accepts. No sibling tool in the list does anything similar, so the agent can identify it immediately.

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?

Explicitly names the triggering conditions ('errors, unexpected behaviour, or the user expresses frustration') and tells the agent how to behave toward the user ('briefly mention it... but do not ask for permission first'). This is a rare case of both when-to-use and interaction protocol being spelled out.

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