No user-submitted related servers found.
Scored across 39 tools
Most tools are clearly separated by domain prefix and action, but there are several near-overlaps such as kusto_command vs kusto_show_command, eventstream_get_definition vs eventstream_get_current_definition, and eventstream_create vs eventstream_create_from_definition. Descriptions help clarify the intended use, but an agent could still plausibly select the wrong tool in these cases.
Tool names consistently use snake_case with domain prefixes like kusto_, eventstream_, map_, and activator_, and most follow a verb_noun pattern. Minor deviations such as kusto_known_services, kusto_diagnostics, and the overloaded eventstream_*_definition names keep it from being perfectly consistent.
With 39 tools, the server is heavily loaded and exceeds the 25-tool threshold for a typical MCP surface. The count reflects the broad Fabric RTI scope, but the toolset would be easier for agents to navigate if split into more focused servers per domain.
Kusto, Eventstream, and Map have strong coverage with querying, schema inspection, ingestion, lifecycle management, and definition editing. However, Activator is notably thin: only artifact listing and trigger creation exist, with no way to get, update, list, or delete existing triggers, leaving an obvious management gap.