Skip to main content
Glama

submit_feedback

Send feedback, a bug report, or a feature request to the Klyf team. If the user reports a specific problem or makes a specific request, even in one line (like 'the audit crashed on my last video' or 'let me export my winners to a spreadsheet'), send it right away this turn with kind set to bug, feature, or general; you can still ask a follow-up after. Only when the complaint is too vague to categorize (like 'something is wrong' or 'Klyf doesn't work' with no specifics) ask one short follow-up to pin down what happened, then send. A bug report about a Klyf tool (like a crashed audit) is feedback to log here, not a request to run that tool.

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
kindNobug for a problem or something broken, feature for a request or suggestion, general for other feedbackgeneral
messageYesA clear, specific description of the bug, feature request, or feedback

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the bar is lower; the description still adds real behavior: submit without delay, at most one clarifying question, and only for uncategorizable complaints. It stops short of saying what happens after submission (confirmation, whether the team responds), which keeps it off 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?

Front-loaded with the action and then the routing rule, and the examples ("the audit crashed on my last video") do real work by anchoring the categorization. It runs slightly long, and "you can still ask a follow-up after" is a soft redundancy, but nothing is filler.

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 two-parameter, non-destructive write tool with no output schema, the description covers the triggering conditions, the categorization rule, and the sibling-tool confusion case. The only missing piece is post-submission behavior, which is minor given the tool's simplicity.

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%, so the baseline is 3, but the description goes beyond the enum's own text by giving concrete decision rules for `kind` — a crashed audit maps to bug, an export request to feature — which is genuinely useful classification guidance the schema does not provide.

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 states a specific verb and resource ("Send feedback, a bug report, or a feature request to the Klyf team") and explicitly distinguishes this from every sibling by noting that a bug report about a Klyf tool is logged here rather than triggering that tool.

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 explicit when-to-use guidance (send immediately this turn if the user reports a specific problem or request, even one line), an explicit when-not path (only ask a follow-up when the complaint is too vague to categorize), and an explicit disambiguation rule against running the referenced sibling tool.

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