Skip to main content
This page covers how to phrase a question so the Kubit MCP server builds the report you want. It lists the parts of a good prompt, examples from simple to advanced and tips for follow-ups. Each report page has prompts specific to that report type.

​
What a good prompt includes

A Kubit prompt names what to measure and over which time period. The Kubit MCP server fills in the rest with defaults, so add the other parts when the default isn’t what you want. Use the names of events and fields as they appear in your workspace. If you don’t know a field’s name, ask “Which field holds the value Premium?” and the assistant looks it up with explain_field.

​
Examples by complexity

These prompts show how much detail the Kubit MCP server can take in one request.

​
Prompts by report type

Each report page explains what that report needs in a prompt and lists examples.

​
Tips

These tips cover the follow-ups people ask most often after the first report.
  • Ask for a refresh when the data looks old. Saved reports can return cached results. “Refresh it” runs the report again on current data.
  • Ask for rows behind a number. “Show me the traces with errors in the last hour” lists the matching traces, with a link to a CSV export of all of them.
  • Open the report in Kubit for chart settings. The MCP server can’t change number formats, units or colors. Every report it builds comes with a link to the report in Kubit.
  • Switch workspaces before you ask. The MCP server works in one workspace at a time. Ask “Switch to the staging workspace” first, then ask your question.
  • Expect a new report when you change one. Reports can’t be edited through the MCP server. “Same report, but by week” builds a new report and leaves the original as it was.