Bella
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BELLA_AUTH_MODE | No | Authentication mode for Bella MCP. One of: none (default, for stdio/local dev), jwt (tokens from any IdP), github (OAuth 2.1 login via GitHub for claude.ai custom connectors). | none |
| BELLA_LOCAL_ROLE | No | Role assigned to the local user when BELLA_AUTH_MODE is none. One of: viewer, analyst, admin. | analyst |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sales_summaryA | Revenue, orders, units, average order value and margin %, grouped by month, category, region or channel. Uses the official revenue definition (completed + shipped orders, net of discounts). Example: "how did revenue evolve this year?" -> group_by="month", start_date="2026-01-01". |
| top_customersA | The customers who generated the most revenue in a period, with order count and last order date. Optionally filter by segment (Consumer, SMB, Enterprise). Emails are only shown to roles with bella:pii. |
| inventory_alertsA | Products at or below their reorder level, most urgent first. For each: stock, reorder level, units sold in the last 90 days, days of cover left at that pace, and a suggested reorder quantity (enough for ~45 days, at least 2x the reorder level). |
| customer_profileA | A 360° view of one customer: profile, lifetime revenue, orders, favourite category and last 5 orders. If several customers match a partial name, returns the candidates so you can ask which one. |
| ask_bellaA | Ask Bella anything about Brightline Outdoor's data that the preset tools don't cover. Bella turns plain-English questions into SQL using the company's business definitions, runs it safely (read-only, row and time limits) and returns the rows plus the SQL she used. You may also send a SELECT yourself. Returns at most 200 rows: aggregate in SQL when possible. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| monthly_business_review | A ready-made monthly business review (MBR) using Bella's tools. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| schema | Tables, columns and the business glossary (what 'revenue', 'AOV', 'active customer' mean). |
TDQS
Scored across 5 tools
The four preset tools target clearly distinct resources: revenue over time, ranked customers, low-stock products, and a single customer's 360 view. The only overlap is ask_bella, a free-form SQL tool that could answer anything the presets answer, though its description explicitly scopes it to questions the presets don't cover.
All five names are lowercase snake_case descriptive noun compounds (sales_summary, top_customers, inventory_alerts, customer_profile, ask_bella). No mixing of conventions, camelCase, or ad-hoc verbs.
Five tools is well-scoped for a conversational analytics server: four focused presets plus one general query fallback. Each tool clearly earns its place and there is no bloat.
Core analytics workflows are covered: revenue trends, customer ranking, customer detail, and inventory reordering, with ask_bella filling any remaining gap (e.g. product-level, order-level, or ad-hoc questions). The catch-all softens what would otherwise be notable gaps, though agents must fall back to free-form SQL for anything outside these four lenses.