Excel MCP Server

Overview Schema Source Related Servers Discussions Admin

statistical_analysis

Perform statistical analysis on a column in Excel or CSV files to calculate descriptive statistics and identify patterns in your data.

Instructions

Perform comprehensive statistical analysis on a column

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": {
      "filePath": "<filePath>",
      "column": "<column>"
    },
    "name": "statistical_analysis"
  }
}

Input Schema

Name	Required	Description
`filePath`	Yes	Path to the CSV or Excel file
`column`	Yes	Column name or index (0-based)
`sheet`	No	Sheet name for Excel files (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 2, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'comprehensive statistical analysis' but doesn't specify what analyses are performed, output format, error handling, or performance considerations. This leaves critical behavioral traits undefined for a tool with potential complexity.

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, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized for its purpose, though it could be more front-loaded with key details given the lack of other guidance.

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

Completeness2/5

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

Given the tool's potential complexity (statistical analysis), no annotations, no output schema, and many sibling tools, the description is incomplete. It fails to explain what 'comprehensive' means, output expectations, or how it differs from other analysis tools, leaving significant gaps for effective use.

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 schema fully documents the three parameters (filePath, column, sheet). The description adds no additional meaning beyond the schema, such as examples or constraints, but the high coverage justifies a baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'perform[s] comprehensive statistical analysis on a column,' which provides a clear verb ('perform') and resource ('column'), but it's vague about what 'comprehensive statistical analysis' entails. It doesn't differentiate from siblings like 'data_profile,' 'correlation_analysis,' or 'trend_analysis,' leaving ambiguity in its specific purpose.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. With many sibling tools for data analysis (e.g., 'correlation_analysis,' 'trend_analysis,' 'data_profile'), the description lacks context on its unique application, prerequisites, or exclusions, offering no help in tool selection.

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