data-analysis-agent

Overview Schema Source Related Servers Discussions Admin

convert_column_type

Change a dataset column's data type to int, float, string, datetime, or category. Reversible conversion supports data cleaning and analysis.

Instructions

Convert column data type to 'int', 'float', 'str', 'datetime', or 'category'. Reversible.

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>",
      "target_type": "<target_type>"
    },
    "name": "convert_column_type"
  }
}

Input Schema

Name	Required	Description	Default
`column`	Yes
`session_id`	Yes
`target_type`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 4, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose one important trait—'Reversible'—which signals that the operation can be undone. However, it does not explain what happens to incompatible values, missing data, or the session state beyond the fact of reversibility.

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 two short sentences with zero fluff. The main action and target types are front-loaded, and the reversibility note is a separate, valuable piece of information. Every word earns its place.

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?

For a relatively simple transformation tool with an output schema, the description covers the core action and the reversibility trait. However, it lacks guidance on parameter semantics and edge-case behavior, and it does not place the tool in the context of sibling alternatives. It is adequate but not 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. It repeats the target_type enum values already present in the schema but provides no added meaning for session_id or column, and does not explain how these parameters interact or what constraints apply. The added value over the structured schema is minimal.

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 uses a specific verb ('Convert') with a clear resource ('column data type') and enumerates the exact allowed target types. This sharply distinguishes it from sibling tools like drop_column or rename_column without needing to inspect their schemas.

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?

Beyond noting that the operation is reversible, the description gives no guidance on when this tool should be used versus alternatives like handle_missing_values or rename_column. There are no preconditions, no exclusions, and no mention of how it fits into a transformation workflow.

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