No user-submitted related servers found.
Scored across 44 tools
Most tools map to a clear resource+action, but some pairs blur together: node_update vs node_update_config, node_get vs node_find_existing_buttons, and node_connect vs node_get_scheme_edges require reading descriptions to pick correctly. The payment_account_get_by_user vs payment_account_get_by_project pair is a similar near-duplicate. Three sub-domains (automation, analytics, payments) are otherwise cleanly separated.
The whole surface is snake_case and predominantly follows resource_verb ordering (project_create, scheme_get, node_delete, analytics_export_status). A few deviations like get_nodes_info use verb-first ordering, and grouping prefixes are long but predictable. Minor inconsistencies, not confusing.
44 tools is heavy for the apparent scope, especially since a large block (analytics_*, payment_account_*) belongs to adjacent but separable products. Many near-sibling tools (node_process_*, scheme_process_*, analytics_export_*) inflate the surface and hurt discoverability for an agent choosing among them.
Coverage is strong: full CRUD on projects, schemes, nodes, edges, and processes, plus import/export, swagger generation, analytics orgs/projects/event-types/exports, and payment transactions. Gaps are minor — e.g., no payment account creation/linking tool and no analytics event-type detail/edit, but agents can work around these.