Skip to main content
Glama
bluebonnet-sales

bluebonnet-sales

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BLUEBONNET_DBNoPath to the SQLite database file. Defaults to bluebonnet.db in the project folder.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_tablesA

List the tables in the database with their row counts.

describe_tableB

Show a table's columns, types and keys.

run_queryA

Run one read-only SQL SELECT and return up to 200 rows.

Anything that would change data, attach another database or change settings is refused. Queries are stopped after 5 seconds.

sales_summaryA

Revenue, order count and average order value between two dates (YYYY-MM-DD, inclusive).

Cancelled orders are left out.

top_customersB

The customers who spent the most, optionally between two dates (YYYY-MM-DD).

low_stockA

Products with stock at or below a threshold, lowest first.

update_order_statusA

Change an order's status. Without confirm=True this only previews the change.

Delivered and cancelled orders are final and can't be changed.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation4/5

The schema tools (list_tables, describe_table, run_query) and the canned reports (sales_summary, top_customers, low_stock) each target a clearly different question, and update_order_status is the only mutating tool. The one soft overlap is that run_query could reproduce any of the report tools, so an agent must decide between a prebuilt report and ad-hoc SQL, but the descriptions make the intended choice reasonably clear.

Naming Consistency4/5

All names are consistently snake_case and readable. The verb_noun pattern holds for list_tables, describe_table, run_query and update_order_status, but the three report tools (sales_summary, top_customers, low_stock) drop the verb and use noun phrases, a minor deviation from an otherwise predictable convention.

Tool Count5/5

Seven tools is well-scoped for a sales-database server: three discovery/query primitives, three focused reports, and one guarded write. Nothing feels redundant or padded, and there is no obvious missing operation forcing extra tools.

Completeness4/5

The surface covers schema discovery, arbitrary read queries, common sales analytics, inventory alerts, and a confirmed order-status update. There is no detail-level order/customer lookup or any create/delete path, but run_query serves as an escape hatch for read gaps, so the omissions are workaround-able rather than dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues