data-analysis-agent

Overview Schema Source Related Servers Discussions Admin

frequency_analysis

Count occurrences of each value in categorical or discrete columns, returning the top N most frequent values to reveal distribution patterns and dominant categories.

Instructions

Calculate frequency distribution and value counts for categorical or discrete columns (top N most frequent).

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": {
      "session_id": "<session_id>",
      "column": "<column>"
    },
    "name": "frequency_analysis"
  }
}

Input Schema

Name	Required	Description	Default
`top_n`	No
`column`	Yes
`sample`	No
`session_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 4, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. 'Calculate' implies a read-only operation, and an output schema exists, so return-value details are covered elsewhere. However, the description does not disclose how missing values, sampling, or session state are handled, leaving some behavioral ambiguity.

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?

The description is a single concise sentence with no filler. It front-loads the core purpose, adds the categorical/discrete qualifier, and states the top-N behavior, all without redundancy.

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

Completeness3/5

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

The tool is relatively simple and has an output schema, but the description omits important context such as how the 'sample' parameter behaves and when this tool should be preferred over similar siblings like 'compute_statistic' or 'group_analysis'. It is adequate but not fully complete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for explaining the parameters. It indirectly explains 'column' and 'top_n' through 'categorical or discrete columns' and 'top N', but it does not explain 'sample' or 'session_id'. This is a meaningful gap for correct invocation.

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 states a specific verb ('calculate'), a clear resource (frequency distribution/value counts), and a scope ('categorical or discrete columns'). The phrase 'top N most frequent' clarifies the output, and the categorical/discrete qualifier helps differentiate this from numeric statistics tools.

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 clear usage context: use for categorical or discrete columns and request the top N most frequent values. It does not explicitly name sibling tools or provide when-not-to-use guidance, but the intended use case is clear enough for selection.

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