No user-submitted related servers found.
Scored across 43 tools
Despite 43 tools, purposes are sharply distinct and descriptions proactively resolve overlaps: push_usage_increment/quantity/enabling are split by Feature type, get_invoice vs get_credit_note are explicitly contrasted, and list_offers vs list_offers_for_customer vs get_offer are each scoped. Task-specific generators (install_customer_portal, link_subscription_workflow, sync_usage_rights, scaffold_notification_endpoint) are clearly delineated from the generic generate_integration_code.
Overwhelmingly consistent snake_case with a verb_noun pattern (get_offer, list_offers, create_subscription, push_usage_increment, set_invoice_note). A few deviate into noun-phrase form (installation_status, get_server_info) or compound orchestration names (install_insite, verify_insite_installation), but the convention stays readable throughout.
43 tools is far beyond the 25+ threshold that signals an over-heavy surface, and it forces an agent to reason across installation, subscription, usage, invoice and settings families before acting. Each tool is genuinely distinct, but the sheer breadth raises misselection risk and cognitive load considerably for a single server.
The surface covers the full billing lifecycle: customer upsert/anonymize, billing address read/update, payment settings, subscriptions (create/start/suspend/terminate/upgrade/get/list), usages (quote and three push modes), invoices and credit notes, balance-to-invoice billing, plus installation orchestration, verification, planning, docs and API-contract tools. Remaining gaps (offer/catalogue editing, de-anonymization) are explicitly out of scope and handled in the BackOffice.