Tell us what broke, or ask your agent to.
People use the form. AI agents can report a problem over MCP, from inside the session where it happened, with the exact call, URL and result already in hand.
The best bug report comes from the session where it happened
Levirge Search has a feedback tool. Any MCP client connected to Search can call it, and the report goes to the Levirge Search team.
| Argument | What goes in it |
|---|---|
| feedback | What was done, what was expected and what happened (10–4000 characters). |
| tool | Which tool misbehaved: fetch, search, … |
| context | The URL or query involved. |
Each call adds a new report; nothing is changed or removed. Good reasons to call it: a wrong or garbled body, bad routing, missing search results, or confusing select/schema behaviour.
| Add one line to your agent's instructions |
|---|
| If a Levirge Search tool returns something wrong or surprising, call feedback with what you did, what you expected and what happened. |
Levirge Brain: feedback teaches ranking
Brain's tool doesn't send us a message. After a search, the agent marks a result helpful, a bounded ranking lift, or dead_end, which down-ranks it and feeds gap analysis. To report a problem with Brain itself, use the form.
Levirge DevOps
In private testing, and it doesn't have a feedback tool over MCP. Use the form.
What did you do, expect, and get?
Include the URL, query or tool call if you have it.
Message received
Thanks — we'll reply within one business day.
Feedback, from people and agents
Can my AI agent send feedback to Levirge?
Yes, for Levirge Search. Its MCP server has a feedback tool that sends a report to the Levirge Search team: what was done, what was expected and what happened, plus the tool and the URL or query involved. Any MCP client connected to Search can call it.
What does Levirge Brain's feedback tool do?
It teaches ranking rather than sending us a message. After a search, an agent marks a result helpful, which gives it a bounded ranking lift, or a dead end, which down-ranks it and feeds gap analysis. To report a problem with Brain itself, use the form.
What should a good report include?
What you did, what you expected and what happened instead, with the exact URL, query or tool call. A report sent by the agent from the session where the problem happened usually has all of this already.
How do I give feedback on Levirge DevOps?
Use the form. Levirge DevOps is in private testing and does not have a feedback tool over MCP.
What happens to my feedback?
It goes to the team that runs the product. Under our terms, feedback you choose to give may be used to improve the services without obligation.