Skip to main content
Glama
ambermem

Amber

Official
by ambermem
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

amber_send_feedback_to_developer

Send structured bug reports or feature requests to improve memory persistence. Include category, summary, and reproduction details for efficient developer triage.

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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
summaryYesOne sentence, under 100 chars. E.g. 'Search misses memories stored with emoji in content'.
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.'
tool_contextNoThe specific amber_ tool name involved, e.g. 'amber_search_memories'. Helps route the report.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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."
  2. 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'."
  3. 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."
  4. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses rate limiting (bucket 12, refill 1 per 5 min) and security constraints (never include passwords). It tells the agent to mention it to the user after sending. It does not describe error handling or asynchronous behavior, but overall is fairly transparent.

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?

The description is concise (4 sentences), front-loaded with purpose, then usage guidelines, security, and rate limit. Every sentence adds unique value without repetition.

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?

Given no output schema, the description covers purpose, usage, behavior, and parameter constraints adequately. It lacks details about return values or confirmation, but the context is otherwise sufficient for effective tool use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 4 parameters. The description adds value beyond the schema by providing a security warning applicable to all fields and clarifying that tool_context should be an amber_ tool name. This enhances understanding.

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?

The description clearly states it sends structured feedback (bug report, feature request, or general) to Amber's developer. It uses a specific verb ('send') and resource ('feedback to developer'), and distinguishes from siblings which handle memory/account operations.

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 provides explicit guidance on when to send feedback proactively (errors, unexpected behavior, user frustration) and instructs not to ask for permission. It also warns against including sensitive info. However, it does not explicitly rule out other inappropriate uses, though context implies appropriate usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ambermem/amber'

If you have feedback or need assistance with the MCP directory API, please join our Discord server