mcp-server-playground
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_HOST | No | Host for the Streamable HTTP server. Defaults to 127.0.0.1. | 127.0.0.1 |
| MCP_HTTP_PORT | No | Port for the Streamable HTTP server. Defaults to 4871 for plain HTTP and 4872 for the OAuth variant. | 4871 |
| MCP_SQLITE_DB | No | Override the database path. Defaults to data/shop.db resolved relative to the project root. | data/shop.db |
| MCP_SQLITE_PERSIST | No | Set to 1 to skip the database reset and reuse the existing database. Defaults to false (reset on each start). | 0 |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesA | List every table in the store database with its row count. Start here when exploring. |
| describe_tableA | Show the column definitions and three sample rows for one table. |
| search_productsB | Find products by keyword, category, price range or stock availability. |
| customer_ordersA | Look up a customer by id, email or partial name, and return their orders with line items already joined. |
| sales_summaryA | Aggregate sales over a date range, grouped by month, product category, brand, customer prefecture or order status. Cancelled orders are excluded unless grouping by status. |
| top_productsA | Rank products by revenue, units sold or average review rating over a date range. |
| search_reviewsA | Full-text search over review bodies. Returns matching reviews with the product they are about. Use this for questions about what customers say ("どの商品で破損の報告が多い?"), as opposed to search_products which only matches product names. |
| add_reviewB | Insert a new review row for a product. This modifies the database. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| monthly_report | Draft a sales report for one month using the store data. |
| product_deep_dive | Investigate one product: sales trend, reviews, and who buys it. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| database-schema | Full CREATE TABLE statements for every table in the store database. |
| customers (sample rows) | First 5 rows of a table, as JSON. |
| order_items (sample rows) | First 5 rows of a table, as JSON. |
| orders (sample rows) | First 5 rows of a table, as JSON. |
| products (sample rows) | First 5 rows of a table, as JSON. |
| reviews (sample rows) | First 5 rows of a table, as JSON. |
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: table exploration, product lookup, customer orders, sales aggregation, product ranking, review search, review insertion, and table listing. The description for search_reviews explicitly contrasts it with search_products, eliminating any ambiguity.
Names are all lowercase with underscores, but conventions mix: four use verb_noun (describe_table, search_products, add_review, list_tables) while the rest are noun phrases (customer_orders, sales_summary, top_products). This is readable but not a uniform pattern.
Eight tools is well-scoped for an e-commerce analytics/playground server. Each tool covers a distinct capability (exploration, search, reporting, review handling) without bloat or thinness.
The tool surface covers exploration, search, analytics, and review insertion comprehensively. Minor gaps exist (no update/delete for reviews, no CRUD for products/customers), but these are likely outside the server's read-oriented analytics purpose.