No user-submitted related servers found.
Scored across 7 tools
Most tools target clearly distinct operations: connection switching, health check, schema introspection, raw SQL, and OData reads/writes. The only real overlap is execute_service_layer_write vs execute_service_layer_write_unattended, which differ solely in approval mode, but the descriptions explicitly state when to use each, mitigating confusion.
All tools use snake_case with a predictable verb_noun (or verb_resource) structure: connect_database, execute_sql, check_connection, get_schema_info, execute_service_layer, and the consistent _write / _write_unattended suffixes. No mixed conventions.
Seven tools is well-scoped for a database + Service Layer bridge: connection, health, schema, SQL read, SL read, SL write, and unattended write. Each tool earns its place; nothing feels redundant beyond the necessary approval-mode split.
The surface covers the full read lifecycle (connect, check, schema, SQL, OData GET) plus guarded writes, with the deliberate and documented omission of raw SQL writes. The main gap is the lack of Service Layer metadata/entity-set discovery analogous to get_schema_info, which would help agents construct valid OData requests.