Skip to main content
Glama

send_feedback

Report bugs, friction, or feature ideas about VibeView itself to its team, showing the user the draft and getting approval before sending.

Instructions

Send the VibeView team a bug report, a friction note or a feature idea about VibeView itself. Only for problems with VibeView itself (the CLI, MCP tools, devices, sessions, runs, dashboard, docs) — never for bugs in the user's own app. Show the user what you will send and get their OK first. Never include passwords, tokens, API keys, test data values or personal data. One report per problem; do not resend it. kind: bug (something broke), friction (it worked but was confusing, slow or awkward), idea (a missing capability). user_quote: the user's own words, verbatim — never a paraphrase. The report includes the session's device and status when it names one.

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": {
      "kind": "<kind>",
      "summary": "<summary>"
    },
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesbug, friction or idea.
detailsNoWhat you tried, what happened, what you expected; kept to 4000 characters.
summaryYesOne line; kept to 200 characters.
session_idNoSession ID to target. Optional: falls back to the MCP-server-held dev_start session, then this project's `vibeview dev --detach` state, if either is available.
user_quoteNoThe user's own words about the problem, verbatim (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false; the description adds the important context that this transmits data to a third party (the VibeView team), requires user consent beforehand, must exclude secrets and personal data, and should not be duplicated. It does not describe what confirmation or response the agent gets back, which keeps it from 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 purpose and scope, and every clause carries operational content. There is mild redundancy between 'about VibeView itself' and the follow-up 'Only for problems with VibeView itself', and the run-on dash structure makes it slightly dense, but nothing is wasted.

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?

For a 5-parameter write tool with no output schema, the definition covers scope, consent protocol, privacy constraints, deduplication, enum semantics and implicit session context — everything an agent needs to invoke it correctly.

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 already 100%, so baseline is 3, but the description meaningfully glosses the 'kind' enum (bug = something broke, friction = worked but confusing/slow/awkward, idea = missing capability) and reinforces that user_quote must be verbatim rather than paraphrased. It also notes the report auto-includes session device and status, which the schema does not state.

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 the VibeView team a bug report, a friction note or a feature idea') and explicitly scopes the target to VibeView itself, listing the concrete subsystems covered (CLI, MCP tools, devices, sessions, runs, dashboard, docs). No sibling tool does this, so an agent can distinguish 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?

Gives explicit when-to-use ('problems with VibeView itself') and when-not ('never for bugs in the user's own app'), plus procedural guidance: show the user what will be sent, get their OK first, and one report per problem with no resends.

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