Elekto MCP for SQL Server

Official

Overview Schema Source Related Servers Discussions Admin

Profile column data

get_data_profile

Read-onlyIdempotent

Profiles table or view columns to reveal null ratios, distinct counts, minimum/maximum values, and top values, so you can understand data distribution without paging through rows.

Instructions

Profiles the columns of one table or view: null ratio, distinct count, minimum, maximum and most frequent values. Use it to learn how data is distributed without paging through rows with query_table. It reads actual row values and scans the table, so on a large table it can take a while; limit it to the columns you need.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "database": "<database>",
      "table": "<table>"
    },
    "name": "get_data_profile"
  }
}

Input Schema

Name	Required	Description
`table`	Yes	Table name, bare, with no schema prefix.
`schema`	No	Table schema. Empty means dbo. Example: 'Feeder'
`columns`	No	Columns to profile as ONE comma-separated string, not a JSON array. Example: 'Source, Name'. Empty profiles every column.
`database`	Yes	Name of the database as registered in the configuration.
`top_values`	No	Top frequent values to return per column (default 5).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish that this is a safe, idempotent, non-destructive read, so the description needn't restate safety. It does add genuinely useful behavioral context beyond the annotations: it 'reads actual row values and scans the table', so on a large table 'it can take a while'. That performance warning is the kind of thing an agent needs and annotations cannot convey.

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

Conciseness5/5

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

Two dense sentences with zero filler: the first defines what it returns, the second covers usage and cost. Nothing is buried and nothing is repeated from the schema.

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?

With no output schema, the description compensates by naming the exact metrics returned per column, and it flags the cost profile of the operation. For a read-only profiling tool of this complexity, an agent has everything needed to call it correctly.

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 description coverage is 100%, so all five parameters are already documented, including the comma-separated column format and the top_values default. The description only echoes the columns-scoping idea ('limit it to the columns you need') without adding syntax or format detail. Baseline 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?

States a specific verb (profiles) and resource (columns of one table or view), then enumerates the exact metrics returned: null ratio, distinct count, min, max, most frequent values. This is unmistakable against siblings like query_table or get_table_schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent away from the alternative: 'without paging through rows with query_table', and adds the scoping advice 'limit it to the columns you need'. Both when-to-use and a practical constraint are stated.

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