Skip to main content
Glama
Datris MCP Server

Datris MCP Server

profile_data

Generate column-level summary statistics, detect data quality issues, and get suggested validation rules from CSV data using AI. Use returned aiRule values in pipeline dataQuality sections.

Instructions

Send data and use AI to generate a comprehensive data profile: summary statistics per column, data quality issues detected, and suggested validation rules. Use the suggested aiRule when building a pipeline's dataQuality section. The server may withhold row values from the model (DATRIS_AI_SAMPLE_VALUES=false): the profile is then built from column statistics or structure only, sampleValues are empty, and the result carries valuesWithheld: true. If the AI model declines the request (a provider safety decline), the result carries aiDeclined: true and holds the server's column statistics only, with empty qualityIssues and recommendations: read that as no AI review, not as a clean file.

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": {
      "content": "<content>",
      "filename": "<filename>"
    },
    "name": "profile_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
headerNoWhether CSV has a header row (default: true)
contentYesBase64-encoded file content
filenameYesFilename (e.g., sample.csv)
delimiterNoCSV delimiter (default: comma)
sample_sizeNoNumber of rows to sample for profiling (default: 200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and largely meets it, disclosing the privacy mode (DATRIS_AI_SAMPLE_VALUES=false yields valuesWithheld: true and empty sampleValues) and the safety-decline path (aiDeclined: true with empty qualityIssues and recommendations, explicitly not a clean file). That is unusually strong failure-mode disclosure. It still does not mention cost, latency, or that this routes data to an external model provider, so it is not exhaustive.

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 purpose statement is front-loaded and each subsequent sentence adds a distinct operational fact about a degraded result mode. The final two sentences are long and clause-heavy, but no sentence is filler.

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?

There is no output schema, so the description must characterize the return value, and it does so for both success (statistics, qualityIssues, recommendations, aiRule) and the two degraded paths. For a five-parameter profiling tool with no annotations this is nearly sufficient, missing only basic cost or latency expectations.

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 the parameters (header, content, filename, delimiter, sample_size) are already fully documented and the baseline is 3. The description adds only indirect meaning, tying sampleValues and withholding behavior to the sampling concept rather than explaining any parameter in greater depth.

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 first sentence states a specific action and output: send data, use AI to produce a profile with summary statistics per column, quality issues, and suggested validation rules. That is concrete enough to distinguish it from upload_data or find_data without opening the schema, and the named artifacts (aiRule, dataQuality) tie it to a definable output.

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?

The description gives a clear forward-use instruction: 'Use the suggested aiRule when building a pipeline's dataQuality section,' which tells the agent where the output belongs in a workflow. It does not enumerate when not to call this versus siblings such as upload_data or find_data, so it falls short of a full when/when-not treatment.

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

Deploy Server

Other Tools