Skip to main content
Glama
DimiDR

SAP Datasphere MCP Server

by DimiDR

analyze_column_distribution

Analyze a column's data distribution to detect outliers, nulls, and patterns, enabling data quality assessment and profiling before analytics.

Instructions

Perform advanced statistical analysis of a column's data distribution including nulls, distinct values, percentiles, and outlier detection.

Use this tool when:

  • User asks "What's the data quality of AMOUNT column?"

  • Performing data profiling before analytics

  • Assessing column completeness and distribution

  • Detecting outliers and data anomalies

  • Understanding data patterns for ML/AI

What you'll get:

  • Basic statistics (count, nulls, distinct values, completeness)

  • Numeric statistics (min, max, mean, percentiles)

  • Distribution analysis (top values, frequency)

  • Outlier detection (IQR method)

  • Data quality assessment

Use cases:

  • Data quality assessment

  • Pre-analytics data profiling

  • Outlier and anomaly detection

  • Understanding value distributions

  • ML feature engineering preparation

  • Data cleansing planning

Example queries:

  • "Analyze the distribution of SALES_AMOUNT column"

  • "What's the data quality of CUSTOMER_AGE?"

  • "Profile the ORDER_STATUS column"

  • "Detect outliers in PRICE column"

  • "Show me statistics for QUANTITY field"

Analysis includes:

  • Null percentage and completeness rate

  • Distinct value count and cardinality

  • For numeric columns: min, max, mean, percentiles (p25, p50, p75)

  • Top value frequencies

  • Outlier detection using IQR method

  • Data quality recommendations

Performance notes:

  • Analyzes up to 10,000 records (configurable)

  • Default sample size: 1,000 records

  • Works with numeric, string, and date columns

  • Automatic type detection and appropriate statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesSpace ID containing the asset (e.g., 'SAP_CONTENT', 'SALES_ANALYTICS')
asset_nameYesAsset (table/view) name containing the column
column_nameYesColumn name to analyze (e.g., 'SALES_AMOUNT', 'CUSTOMER_AGE', 'ORDER_STATUS')
sample_sizeNoOptional: Number of records to analyze (10-10000). Default: 1000. Larger samples = more accurate but slower.
include_outliersNoOptional: Detect and report outliers using IQR method. Default: true
Behavior4/5

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

Without annotations, the description carries the full burden and discloses key behaviors such as sampling up to 10,000 records, default sample size 1,000, support for numeric/string/date columns, and automatic type detection. It does not mention side effects because it is a read-only analysis, but the disclosed operational traits are sufficient for informed use.

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

Conciseness3/5

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

The description is well-structured with sections, but it is lengthy and contains redundancy: 'What you'll get' and 'Analysis includes' overlap, and use cases repeat the 'Use this tool when' content. It could be trimmed significantly without losing value.

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

Completeness5/5

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

Given the absence of an output schema, the description compensates effectively with a 'What you'll get' section that outlines return information, plus performance notes and examples. It covers all essential aspects—purpose, usage, behavior, and parameters—making it complete for an AI agent.

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

Parameters3/5

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

Schema coverage is 100% with detailed descriptions for all parameters, including defaults and bounds (e.g., sample_size min/max, include_outliers default). The description adds little beyond the schema; the 'Performance notes' mostly echo parameter constraints, so the baseline of 3 is appropriate.

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 explicitly states 'Perform advanced statistical analysis of a column's data distribution including nulls, distinct values, percentiles, and outlier detection.' This uses a specific verb and resource, and clearly differentiates from siblings like get_table_schema or execute_query by focusing on distribution profiling and statistics.

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

Usage Guidelines4/5

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

Provides an explicit 'Use this tool when' list and multiple example queries, giving clear context for when to deploy this tool. However, it does not explicitly state when not to use it or name alternative tools, so it falls short of a 5.

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/DimiDR/SAP-Datasphere-MCP'

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