Skip to main content
Glama
microsoft

Microsoft Fabric RTI MCP Server

Official
by microsoft

kusto_diagnostics

Read-only

Runs diagnostic commands on a Kusto cluster and returns a JSON summary of resource utilization, node state, permissions, health, workload groups, rowstores, and recent ingestion failures.

Instructions

Runs a suite of diagnostic commands and returns a JSON summary of the cluster's
current state. Each section runs independently — if a command fails (e.g., due to
permissions or unsupported features), that section returns an error while others
continue normally.

:param cluster_uri: The URI of the Kusto cluster.
:param database: Optional database name. If not provided, uses the default database.
:param client_request_properties: Optional dictionary of additional client request properties.
:return: A dictionary with keys for each diagnostic area. Each value is either a list
         of row-dicts or {"error": "<message>"} if that command failed.

Sections returned:
* capacity — resource utilization limits (total, consumed, remaining per resource)
* cluster — cluster node info and state
* principal_roles — caller's permission scope and role
* diagnostics — internal cluster diagnostics (health, latency, utilization)
* workload_groups — configured workload groups and their policies
* rowstores — rowstore state and memory usage
* ingestion_failures — ingestion failures from the last 24 hours

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cluster_uriYes
databaseNo
client_request_propertiesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false. The description reinforces this by explaining the diagnostic (read-only) nature and adds transparency about partial failure behavior: each section returns errors independently without affecting others.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: first sentence states purpose, then a second paragraph explains error handling, parameter details in param/return format, and a list of sections. It's slightly verbose but every sentence adds value, and front-loading is effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has multiple diagnostic sections and an output schema (though not shown), the description completes the picture by listing the sections and explaining the return format (dictionary with lists or error dicts). It adequately covers behavior, parameters, and return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at 0%, the description carries the full burden. It explains cluster_uri, database, and client_request_properties in the docstring, providing meaning beyond the schema's type definitions. However, it does not give examples or constraints for client_request_properties.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool runs a suite of diagnostic commands and returns a JSON summary of the cluster's current state. It uses specific verbs ('runs', 'returns') and identifies the resource ('Kusto cluster'). Among siblings like kusto_query and kusto_command, this tool is distinct as a comprehensive diagnostics suite.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description notes that sections run independently and handle errors gracefully, but it does not explicitly state when to use this tool versus alternatives like kusto_query or kusto_command. The context implies it's for overall health checks, but clear usage boundaries are missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/microsoft/fabric-rti-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server