Gameball MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub token for higher rate limits when fetching documentation | |
| GAMEBALL_API_KEY | No | Your Gameball API key (required for integration tools) | |
| GAMEBALL_BASE_URL | No | API base URL | https://api.gameball.co |
| GAMEBALL_SECRET_KEY | No | Your Gameball secret key (required for sensitive operations like adjust balance, batch operations, etc.) |
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 |
|---|---|
| docs-lookup-topicA | START HERE. Comprehensive single-call lookup that returns tutorials, related docs, AND relevant API endpoints for a topic. Use this first for any broad question (e.g. "how to create an order with redemption", "referral setup", "customer management"). Only use the other tools if you need to drill deeper into a specific page or endpoint. |
| docs-get-docA | Get the full content of a specific doc page by path. Use after docs-lookup-topic when you need to read a specific page in full. |
| docs-get-api-endpointA | Get full details of a specific REST API endpoint including parameters, request/response schemas, and a cURL example. Use after docs-lookup-topic when you need details on a specific endpoint. |
| docs-generate-code-exampleA | Generate a code example for a Gameball API endpoint in a specific programming language. Use when the user asks for code in a specific language (not cURL, which is already included in docs-get-api-endpoint). |
| docs-search-docsA | Full-text search across all Gameball docs. Returns titles and snippets. Use when docs-lookup-topic did not find what you need or you need to search within a specific section. |
| docs-list-sectionsA | List the documentation structure: tabs, sections, and page slugs. Use when the user wants to browse available topics or you need to discover page paths. |
| docs-get-tutorialA | Get a specific Gameball tutorial by topic. Use when you need the full step-by-step tutorial content. For broad questions, use docs-lookup-topic instead. |
| createCustomerC | Create customer |
| getCustomerD | Get customer |
| deleteCustomerC | 🔒 Delete customer |
| getCustomerDetailsD | 🔒 Get detail |
| getCustomerCouponsD | 🔒 Get coupon |
| achieveSocialChallengeD | 🔒 Create social-challenge |
| getCustomerHashD | 🔒 Get hash |
| validateReferrerCodeD | Get validate |
| calculatePaymentCashbackD | Create cashback |
| getCampaignsConfigurationsC | Get reward-campaign |
| getTiersConfigurationsC | Get tier |
| getReferralsConfigurationsC | Get referral |
| trackOrderC | 🔒 Create order |
| calculateOrderCashbackD | Create cashback |
| getOrderTransactionsC | 🔒 Get transaction |
| getCustomerBalanceC | 🔒 Get balance |
| getCustomerTierProgressD | 🔒 Get tier-progres |
| getCustomerCampaignsProgressD | 🔒 Get reward-campaigns-progres |
| getCustomerReferralsC | 🔒 Get referral |
| getCustomerReferralsCountD | 🔒 Get count |
| getCustomerActivitiesD | 🔒 Get activitie |
| getCustomerActivitiesCountD | 🔒 Get count |
| getCustomerAutomationCampaignsD | Get automation |
| getCustomerStampsProgressD | 🔒 Get stamp |
| getCustomerDailyStreakProgressD | 🔒 Get streak |
| attachCustomerTagsD | 🔒 Create tag |
| removeCustomerTagsD | 🔒 Delete tag |
| removeCustomerTagC | 🔒 Delete tag |
| listCustomerNotificationsD | Get notification |
| getCustomerNotificationsCountD | Get count |
| markNotificationsReadD | 🔒 Update read |
| sendEventsD | Create event |
| gameball-statusA | Shows server health, subsystem status, configuration, and cache info. |
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 40 tools
Many tools target distinct resources (balance, tier progress, referrals, activities), but overlaps exist: getCustomer vs getCustomerDetails, removeCustomerTags vs removeCustomerTag, and the docs-lookup-topic/search-docs and get-doc/get-tutorial pairs could confuse agents.
The tool set mixes two conventions: docs tools use hyphenated lowercase with a docs- prefix (e.g., docs-lookup-topic), while API tools use camelCase verbs (e.g., createCustomer, getCustomer). Pluralization is also inconsistent (removeCustomerTags vs removeCustomerTag).
40 tools is excessive for a single server, especially with ~15 getCustomer* variations. This makes selection harder and suggests tools could be consolidated into parameterized endpoints.
The server covers a broad range of Gameball operations (customers, orders, campaigns, referrals), but lacks obvious operations like updating a customer or fetching a single order. Documentation tools are comprehensive, but the API surface is not fully CRUD-complete.