Skip to main content
Glama
bitrefill

Bitrefill Search and Shop

Official
by bitrefill

categories

Retrieve product categories to organize searches for cryptocurrency gift cards and mobile top-ups on Bitrefill.

Instructions

Get the full product type/categories map. It's suggested to use this tool to get the categories and then use the search tool to search for products in a specific category.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The inline handler function for the 'categories' tool, which returns a JSON-formatted string of the productCategories map.
    server.tool(
      "categories",
      "Get the full product type/categories map. It's suggested to use this tool to get the categories and then use the `search` tool to search for products in a specific category.",
      {},
      async () => {
        return {
          content: [
            { type: "text" as const, text: JSON.stringify(productCategories, null, 2) }
          ]
        };
      }
    );
  • Registration of the 'categories' tool within the registerToolHandlers function using server.tool.
    server.tool(
      "categories",
      "Get the full product type/categories map. It's suggested to use this tool to get the categories and then use the `search` tool to search for products in a specific category.",
      {},
      async () => {
        return {
          content: [
            { type: "text" as const, text: JSON.stringify(productCategories, null, 2) }
          ]
        };
      }
    );
  • The productCategories constant/map that provides the hierarchy of product types and categories, used by the 'categories' tool.
    export const productCategories: ProductCategoriesMap = {
      "giftcards": [
        "all-gift-cards",
        "apparel",
        "automobiles",
        "cruises",
        "ecommerce",
        "electronics",
        "entertainment",
        "experiences",
        "flights",
        "food",
        "food-delivery",
        "games",
        "gifts",
        "groceries",
        "health-beauty",
        "home",
        "multi-brand",
        "music",
        "other",
        "payment-cards",
        "pets",
        "pharmacy",
        "restaurants",
        "retail",
        "streaming",
        "top-products",
        "travel",
        "utility-bills",
        "voip"
      ],
      "refills": [
        "refill",
        "data",
        "pin",
        "bundles",
        "dth"
      ],
      "bills": [
        "all-bills",
        "auto-loans",
        "banking",
        "bill",
        "catalog-sales",
        "cemeteries-funerals",
        "club-membership",
        "commission-businesses",
        "credit-card",
        "education",
        "financial-services",
        "healthcare",
        "hoa-rent",
        "installment-payments",
        "insurance",
        "internet-cable-tv",
        "mortgages-home-equity",
        "mortgages-property-management",
        "phone",
        "press",
        "sanitation",
        "security-monitoring",
        "taxes",
        "water-electricity-gas"
      ],
      "esims": [
        "esim"
      ],
      "crypto-utils": [
        "bitcoin"
      ]
    };
  • Zod schema and TypeScript type definition for the product categories map data structure.
    export const ProductCategoriesMapSchema = z.record(z.array(z.string()));
    
    /**
     * Product types and their associated categories
     */
    export type ProductCategoriesMap = z.infer<typeof ProductCategoriesMapSchema>;
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It indicates this is a read operation ('Get') but doesn't specify whether it requires authentication, has rate limits, returns structured data, or has any side effects. The description adds some context about the relationship with the search tool but lacks comprehensive behavioral details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is perfectly concise with two sentences that each serve distinct purposes: the first states what the tool does, the second provides usage guidance. There's zero wasted language and it's front-loaded with the core functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with no output schema, the description provides adequate context about what the tool returns (a categories map) and how to use it in conjunction with other tools. However, it doesn't specify the format of the returned data or any error conditions, which would be helpful given the lack of output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on the tool's purpose and usage pattern.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with the verb 'Get' and resource 'full product type/categories map'. It distinguishes from sibling 'search' by indicating this tool provides the category mapping while search finds products within categories. However, it doesn't explicitly differentiate from 'detail' or 'ping' tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance: 'It's suggested to use this tool to get the categories and then use the `search` tool to search for products in a specific category.' This gives clear when-to-use context and names a specific alternative tool (search) for related functionality.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bitrefill/bitrefill-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server