No user-submitted related servers found.
Scored across 18 tools
The tools are mostly distinct: catalog exploration tools (sbis_list_sections, sbis_get_section, sbis_search_methods, sbis_map, sbis_describe_method) are clearly separated from execution tools (sbis_call_method, sbis_write_method, sbis_delete_method) and raw variants (sbis_get_raw, sbis_write_raw, sbis_delete_raw). The main ambiguity is between sbis_get_section and sbis_list_sections, which both sound like listing sections, though their descriptions clarify one lists all sections and the other lists endpoints in one section.
All tools follow the sbis_ prefix and use lower_snake_case verbs (check, get, search, map, call, write, delete, fetch, list, add, set, use, remove, describe). The naming is mostly consistent, with minor deviations: sbis_map as a noun-like verb is less descriptive than the others, and sbis_set_key overlaps conceptually with sbis_add_cabinet for credential updates. Overall the pattern is predictable.
18 tools is slightly on the higher side but appropriate for a server that covers both catalog discovery, curated execution, raw execution, and credential/cabinet management. The count is justified by the breadth of the domain and the need for both catalog-driven and raw HTTP access variants.
The server provides complete coverage: discovery (sections, search, map, describe), safe execution (call), write execution (write), destructive execution (delete), raw access for uncataloged endpoints (get/write/delete_raw), pagination handling (fetch_all), and all credential lifecycle operations (list, add, set, use, remove). No significant gaps for the stated purpose of integrating with Saby/marketplace APIs.