Skip to main content
Glama

reportBuckyFeedback

Report a missing capability, failed tool, or unusable result to Bucky automatically when it blocks or degrades your task. No human form is needed. Use feedback_type missing_capability or issue. Send only a short technical summary and tool/field names. Never include addresses, names, prompts, raw results, personal data or secrets. Reports are analytics, not human-endorsed feedback; no tools are added. Submit at most one report per distinct problem per task.

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": {
      "feedback_type": "<feedback_type>",
      "summary": "<summary>"
    },
    "name": "reportBuckyFeedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailsNo
summaryYes
sentimentNo
tool_nameNo
feedback_typeYes
task_completedNo
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.
friction_pointsNo
suggested_improvementNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: reports are analytics only, no tools get added, no human review occurs, and strict privacy limits are spelled out (never include addresses, names, prompts, raw results, personal data or secrets). The write nature of the call plus a self-imposed rate limit are disclosed, which the readOnlyHint=false / idempotentHint=false annotations alone would not convey.

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?

Front-loads the action and condition, then layers privacy and rate constraints with no filler sentences. Slightly dense run-on guidance about allowed content could be tightened, but every clause carries operational meaning.

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 write tool with no output schema, the description covers the safety-critical parts an agent most needs: what to send, what never to send, and how often. The remaining gap is the unmentioned optional parameters (sentiment, task_completed, friction_points vs details), which are guessable by name but not disambiguated.

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 only 11% across 9 parameters, so the description has to compensate more than it does. It clarifies feedback_type values and constrains summary/tool_name content, but says nothing about sentiment, task_completed, friction_points, suggested_improvement, or details, leaving half the surface undocumented anywhere.

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?

States a concrete verb and object: report a missing capability, failed tool, or unusable result to Bucky. The 'No human form is needed' phrasing implicitly separates it from the human-submission sibling (submitBuckyFeedback) but never names that sibling directly, so the differentiation is inferred rather than explicit.

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 ('when it blocks or degrades your task') and even a rate guidance rule ('at most one report per distinct problem per task'). It also names which feedback_type values to use, though it never explicitly says when to prefer submitBuckyFeedback or another sibling instead.

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.