Bitrefill Search and Shop
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITREFILL_API_KEY | Yes | API key for Bitrefill API v2 authentication |
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 |
|---|---|
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| payment-methods | All payment methods accepted by Bitrefill |
| category-slugs | Valid `category` filter values (comma-separated) for GET /products and GET /products/search |
| product-types | High-level product families mapped to B2B category slugs (gift_card, esim, phone_refill, …) |
| gift_card | Categories available for a given product type (URI template) |
| esim | Categories available for a given product type (URI template) |
| phone_refill | Categories available for a given product type (URI template) |
| bill_payment | Categories available for a given product type (URI template) |
| crypto | Categories available for a given product type (URI template) |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no ambiguity: 'categories' retrieves product categories, 'detail' gets product information, 'ping' checks API availability, and 'search' finds products. The descriptions explicitly differentiate their roles, such as suggesting to use 'categories' before 'search' for better context, ensuring an agent can easily tell them apart.
All tool names follow a consistent, simple noun-based pattern (e.g., 'categories', 'detail', 'ping', 'search') without mixing conventions like camelCase or snake_case. This predictability makes the set easy to navigate and understand at a glance.
With 4 tools, the server is well-scoped for its purpose of searching and shopping on Bitrefill. Each tool earns its place by covering essential functions: API health check, category mapping, product search, and detailed product viewing, avoiding bloat or thin coverage.
The tool surface is nearly complete for a search and shop domain, covering discovery (categories, search), inspection (detail), and availability (ping). A minor gap exists in lacking purchase or checkout tools, but agents can work around this by using the provided tools to gather information before external actions.