No user-submitted related servers found.
Scored across 75 tools
Tools are organized by domain (products, placements, airings, campaigns, transactions, POI, reports, logs, auth, utils) and each generally targets a distinct resource+action, with explicit cross-references such as get_transaction_status vs get_transaction_history. A few pairs still blur: validate_jwt vs test_jwt (both JWT debugging), generate_code_example vs generate_documentation (both emit integration guidance), and the four report/export read tools require careful reading to separate. With 75 tools, an agent will occasionally misselect, but the descriptions largely disambiguate.
All names are snake_case with a payware_ prefix and a domain segment, which is readable and predictable at the top level. However the sub-convention varies by domain: products/placements/airings/campaigns use verb_noun (create_product, update_airing), while POI and shops use noun_verb (poi_create, shops_list, poi_set_price). Two tools (generate_code_example, generate_documentation) lack a domain segment entirely, breaking the pattern.
75 tools is heavy for any single agent context, and while the underlying platform is genuinely broad (payments, catalog, placements, campaigns, reporting, logging, auth), many tools are narrow Premium-only CRUD variants (five audio tools, six airing tools, nine data/report tools). The surface could be consolidated into higher-level operations without losing capability, and the sheer count forces expensive tool selection.
Coverage is deep: full CRUD for products, schedules, audio, placements, airings and campaigns, plus transaction lifecycle (create/process/status/history/cancel), POI management, reports/exports and JWT tooling. Minor gaps exist, notably no POI update/delete, no shop management beyond list, no transaction search/listing for merchants, and no refund/settlement operations — workable but not airtight.