Skip to main content
Glama
BACH-AI-Tools

Usage And Billing MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
API_KEYYesAPI 密钥

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_accounts_customersC

Get accounts

get_account_customerC

Get sub-account

get_metersD

Get meters

create_meterC

Create meter

get_plans_of_a_productC

Get plans of a product

create_planC

Create plan of a product.

get_usageD

Get Usage

report_usageD

Report Usage

get_product_itemsD

Get product items

get_productsD

Get Products

create_productC

Create product

get_product_itemD

Get product item

create_product_itemC

Create product item of a product.

get_productD

Get product

delete_productD

Delete product

get_meterC

Get meter

get_my_account_profileB

Get my account

health_checkC

Health check

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.5/5.0

Scored across 18 tools

Disambiguation4/5

Most tools have clearly distinct purposes targeting specific resources like meters, products, plans, and usage, with minimal overlap. However, 'get_account_customer' and 'get_accounts_customers' could cause minor confusion due to similar naming, and 'health_check' is a utility that stands apart from the core billing domain.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern (e.g., create_meter, get_product) with clear CRUD operations, which aids predictability. A minor deviation is 'get_plans_of_a_product' which uses 'of_a' instead of a simpler pattern like 'get_product_plans', slightly breaking the consistency.

Tool Count4/5

With 18 tools, the count is reasonable for a billing and usage management domain, covering various entities like products, meters, and accounts. It's slightly on the higher side but well-scoped, as each tool serves a distinct function without appearing bloated.

Completeness4/5

The tool set provides comprehensive CRUD coverage for core resources (e.g., products, meters, usage) and includes utility functions like health checks. A minor gap is the lack of update or delete operations for meters, plans, and product items, which might require workarounds but doesn't severely hinder core workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues