Skip to main content
Glama
microsoft

Microsoft Fabric RTI MCP Server

Official
by microsoft

kusto_describe_database_entity

Read-only

Retrieve schema information for a specified table, view, or function in your Kusto database to understand its structure and columns.

Instructions

Retrieves the schema information for a specific entity (table, external table,
materialized view, function, graph) in the specified database.
If no database is provided, uses the default database.

:param entity_name: Name of the entity to get schema for.
:param entity_type: Type of the entity (table, external-table, materialized-view, function, graph).
: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: List of dictionaries containing entity schema information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_nameYes
entity_typeYes
cluster_uriYes
databaseNo
client_request_propertiesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds only the return type (list of dicts) and a basic parameter description, but no extra behavioral context such as permissions, side effects, or rate limits.

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 a single paragraph with a clear purpose statement followed by parameter documentation. It is relatively concise but could benefit from more structured formatting (e.g., separate sections).

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 existence of an output schema, the description's mention of return type (list of dicts) is sufficient. It covers all parameters and the default database behavior. For a read-only tool with good annotations, it is adequately complete.

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?

Schema description coverage is 0%, so the description compensates by explaining each parameter (entity_name, entity_type, cluster_uri, database, client_request_properties) and their optionality. This adds meaning beyond the schema's title-only definitions.

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 it retrieves schema information for a specific entity in a Kusto database. The verb 'retrieves' and resource 'entity' are specific, and it distinguishes from siblings like kusto_describe_database (describes database itself) and kusto_list_entities (lists 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?

The description explains optional database usage but does not provide explicit guidance on when to use this tool versus related tools like kusto_describe_database or kusto_list_entities. No alternatives or exclusions are mentioned.

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