Skip to main content
Glama
microsoft

Microsoft Fabric RTI MCP Server

Official
by microsoft

kusto_sample_entity

Read-only

Retrieve a sample of records from a Kusto entity like a table or view. Specify entity name, type, cluster URI, and optional sample size or database.

Instructions

Retrieves a data sample from the specified entity.
If no database is provided, uses the default database.

:param entity_name: Name of the entity to sample data from.
:param entity_type: Type of the entity (table, external-table, materialized-view, function, graph).
:param cluster_uri: The URI of the Kusto cluster.
:param sample_size: Number of records to sample. Defaults to 10.
:param database: Optional database name. If not provided, uses the default database.
:param client_request_properties: Optional dictionary of additional client request properties.
:return: List of dictionaries containing sampled records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_nameYes
entity_typeYes
cluster_uriYes
sample_sizeNo
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. Description adds context: default database handling, parameter descriptions, return type (list of dicts). No contradiction.

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?

Single paragraph clearly front-loaded with purpose. Parameter descriptions are compact and informative. Slightly verbose with :param notation, but efficient overall.

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?

Covers all parameters, defaults, and return type. Output schema exists, so return description is supplementary. Lacks error conditions or edge cases, but adequate for a read-only sample tool.

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

Parameters5/5

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

With 0% schema coverage, description fully compensates: explains each parameter's purpose, default values, and optionality. Adds meaning beyond schema titles.

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?

Precisely states action: 'Retrieves a data sample from the specified entity.' Includes contextual detail about default database. Distinct from siblings like kusto_query and kusto_list_entities.

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?

Mentions database fallback behavior but does not explicitly state when to use this tool over alternatives (e.g., kusto_query or kusto_list_entities). No when-not-to-use guidance.

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