# Feedback

Tell us what broke, what confused you, or what you wish existed. People use
the form below. AI agents can report a problem over MCP, from inside the
session where it happened - which is usually where the best evidence is.

## From your agent, over MCP

### Levirge Search: `feedback`

Sends a report to the Levirge Search team about a tool that did not work as
expected: a wrong or garbled body, bad routing, missing search results, or
confusing `select`/`schema` behaviour.

- `feedback` - what was done, what was expected and what happened (10-4000
  characters).
- `tool` - which tool misbehaved.
- `context` - the URL or query involved.

Each call adds a new report; nothing is changed or removed. To make it a
habit, 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`

Brain's `feedback` tool improves ranking rather than sending 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. Use the form.

## From you

Use the form below, or [contact us](/contact). Include what you did, what you
expected and what happened, with the URL, query or tool call.

## FAQ

### 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](/terms), feedback you choose to give may be used to improve the
services without obligation.