Skip to main content
Glama

Submit feedback to Bucky

submitBuckyFeedback

Open a human-reviewed feedback form and submit it to the Bucky product team. Call only when the user explicitly asks to send feedback, report a problem, suggest an improvement, or praise something. The server asks the MCP client to show the form; nothing is saved unless the human accepts it. Do not use for silent agent self-reporting.

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": {
      "context": "<context>"
    },
    "name": "submitBuckyFeedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftNoOptional. Feedback you drafted from this chat when the user asked you to: what they tried, what went wrong, what they expected. Plain words. No prompts, raw tool output, addresses, names, personal data or secrets. It fills the form for the user to edit.
confirmNoOnly when this client cannot show the form: call first without confirm to get the draft back, show it to the user, and call again with the same draft and confirm: true only after the user says to send it.
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
submissionIdNoOptional. A UUID for this submission; generated server-side when omitted. Pass the same UUID when retrying this exact feedback so it is not recorded twice.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.
affectedToolNameNoTool the user is commenting on, when already known

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / confirm
      Added value: +{
      +  "description": "Only when this client cannot show the form: call first without confirm to get the draft back, show it to the user, and call again with the same draft and confirm: true only after the user says to send it.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / draft
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Optional. Feedback you drafted from this chat when the user asked you to: what they tried, what went wrong, what they expected. Plain words. No prompts, raw tool output, addresses, names, personal data or secrets. It fills the form for the user to edit.",
      +  "properties": {
      +    "affectedToolName": {
      +      "description": "Bucky MCP tool this feedback concerns, when applicable",
      +      "maxLength": 128,
      +      "type": "string"
      +    },
      +    "category": {
      +      "description": "What kind of feedback this is",
      +      "enum": [
      +        "incorrect_result",
      +        "tool_failure",
      +        "missing_capability",
      +        "unusable_result",
      +        "workflow_friction",
      +        "documentation",
      +        "suggestion",
      +        "other"
      +      ],
      +      "type": "string"
      +    },
      +    "expectedOutcome": {
      +      "description": "What should have happened instead, when applicable",
      +      "maxLength": 500,
      +      "type": "string"
      +    },
      +    "impact": {
      +      "description": "Effect on the task; use not_applicable for praise or general suggestions",
      +      "enum": [
      +        "blocked",
      +        "degraded",
      +        "resolved_with_workaround",
      +        "minor",
      +        "not_applicable"
      +      ],
      +      "type": "string"
      +    },
      +    "sentiment": {
      +      "description": "Overall direction of the feedback",
      +      "enum": [
      +        "positive",
      +        "negative",
      +        "neutral"
      +      ],
      +      "type": "string"
      +    },
      +    "summary": {
      +      "description": "Concise feedback. Do not include prompts, tool output, personal data, or secrets.",
      +      "maxLength": 1000,
      +      "minLength": 1,
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / context / description
      Previous value: -"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""New value: +"A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as \"a customer\". Do not quote the user or include names, emails, or other personal details."
  4. Changed2 schema fields changed
    • removedInput schema / properties / llm_model
      Removed value: -{
      -  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "context",
      -  "llm_model"
      -]New value: +[
      +  "context"
      +]
  5. Changed1 schema field changed
    • removedInput schema / properties / conversation_id
      Removed value: -{
      -  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
      -  "type": "string"
      -}
  6. Changed4 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\""New value: +"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "context"
      -]New value: +[
      +  "context",
      +  "llm_model"
      +]
  7. Changed2 schema fields changed
    • changedInput schema / properties / submissionId / description
      Previous value: -"A new UUID generated for this submission. Reuse the same UUID when retrying this exact feedback."New value: +"Optional. A UUID for this submission; generated server-side when omitted. Pass the same UUID when retrying this exact feedback so it is not recorded twice."
    • changedInput schema / required
      Previous value: -[
      -  "submissionId",
      -  "context"
      -]New value: +[
      +  "context"
      +]
  8. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already mark this as a non-read-only, non-destructive, non-idempotent write with no open-world access. The description adds genuinely useful context beyond that: the server asks the MCP client to show a form and nothing is saved unless the human accepts, which tells the agent this is a human-gated write rather than a silent one. It does not add anything about return values or the retry/deduplication path.

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?

Four sentences, front-loaded with the action, then the trigger conditions, then the human-review behavior, then the exclusion. No sentence is filler and the ordering matches how an agent needs the information.

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 six-parameter tool with nested objects and a human-in-the-loop step, the description covers the interaction model, the guardrails, and the privacy expectation well. The gap is that no output schema exists and the description never says what the call returns (for example a submission id or confirmation), which leaves the agent blind on the response shape.

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 the nested draft object is thoroughly documented field by field, including privacy constraints and enums. The description adds no parameter-level meaning beyond the schema; the 'nothing is saved unless the human accepts' line contextualizes the confirm flow only indirectly. Baseline 3 is correct when the schema carries the semantics.

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?

The description names a specific verb and resource: open a human-reviewed feedback form and submit it to the Bucky product team. That is far more than a restatement of the name. It stops short of five because the near-identically named sibling reportBuckyFeedback is never mentioned, so an agent must infer the split between them.

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?

It gives an explicit positive trigger set (user asks to send feedback, report a problem, suggest an improvement, praise something) and an explicit exclusion: 'Do not use for silent agent self-reporting.' That is the when, the when-not, and the constraint that matters most for an autonomous agent.

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.