No user-submitted related servers found.
Scored across 42 tools
Several tools overlap in purpose: smart_query is a composite of execute_query, query_relational_entity, and query_analytical_data, causing ambiguity about which to choose. get_asset_details and get_asset_by_compound_key are nearly identical, differing only in parameter style. Metadata tools like get_relational_metadata and get_relational_entity_metadata have unclear boundaries. However, many tools have distinct scopes and detailed descriptions that help.
Tool names mostly follow a consistent verb_noun snake_case pattern (e.g., list_spaces, create_table, get_task_log). Minor deviations exist: smart_query is a nonstandard compound name and datasphere_cli_status is a noun phrase without a verb. Overall, the naming is predictable and readable.
With 42 tools, the server is overloaded. While SAP Datasphere is a complex platform, this number exceeds the typical 3-15 well-scoped range and includes redundant tools that add confusion without adding functionality. The scope could be split into separate servers (e.g., catalog, query, administration, tasks) to reduce cognitive load.
The toolset covers data discovery, querying, task monitoring, and some administrative functions (database users, table creation), but has notable gaps. There are no tools for updating or deleting tables, managing spaces (beyond listing), creating views, or handling connections beyond listing. The write surface is thin compared to the read surface, and lifecycle operations are incomplete.