mcp-starter-kit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_business_infoA | Returns the business name, contact details, address, and opening hours. Use this to answer questions about the business itself. |
| price_quoteA | Given a service name and quantity, returns the price and a calculated total. Use this when a customer asks how much something costs. |
| lookup_faqA | Searches the business's frequently asked questions for the best match. Use this for common customer questions (wifi, parking, catering, etc.). |
| check_availabilityA | Returns the currently open appointment or booking slots. Use this when a customer wants to book or asks what times are available. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool maps to a distinct resource and intent: business metadata, pricing, FAQ search, and slot availability. There is no realistic overlap that would cause misselection, and descriptions reinforce the boundaries.
All names use snake_case with a leading verb (get_, price_, lookup_, check_), which is consistent and readable. The only minor deviation is get_business_info's three-part name and price_quote's imperative-noun form, but the pattern remains predictable overall.
Four tools is on the low side but appropriate for a lightweight starter kit aimed at basic customer inquiries. Each tool earns its place without redundancy, though the surface is minimal.
The set covers info, price, FAQ, and availability lookups, but there is no tool to actually create or confirm a booking, which is an obvious dead end given check_availability. Adding a booking/contact tool would round out the customer-service lifecycle.