Skip to main content
Glama
shibuiwilliam

MCP Data Wrangler

data_min

Identify minimum values for each column in a dataset using the MCP Data Wrangler server. Analyze data by providing the input file path for streamlined preprocessing and descriptive statistics.

Instructions

Minimum values for each column

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
input_data_file_pathNoPath to the input data file

Implementation Reference

  • The main handler function for the 'data_min' tool, which computes the minimum value for each column in the input dataframe and returns it as JSON.
    async def handle_data_min(
        arguments: dict[str, Any],
    ) -> list[types.TextContent | types.ImageContent | types.EmbeddedResource]:
        data_min_input = DataMinInputSchema.from_args(arguments)
        min_df = data_min_input.df.min()
    
        # Convert the DataFrame to a dictionary format
        min_dict = {
            "description": "Minimum values for each column",
            "min_values": {col: str(val) if val is not None else None for col, val in zip(min_df.columns, min_df.row(0))},
        }
    
        return [
            types.TextContent(
                type="text",
                text=json.dumps(min_dict),
            )
        ]
  • Pydantic schema for input validation of the 'data_min' tool, including static methods to load data from file path argument.
    class DataMinInputSchema(Data):
        model_config = ConfigDict(
            validate_assignment=True,
            frozen=True,
            extra="forbid",
            arbitrary_types_allowed=True,
        )
    
        @staticmethod
        def input_schema() -> dict:
            return {
                "type": "object",
                "properties": {
                    "input_data_file_path": {
                        "type": "string",
                        "description": "Path to the input data file",
                    },
                },
            }
    
        @staticmethod
        def from_schema(input_data_file_path: str) -> "DataMinInputSchema":
            data = Data.from_file(input_data_file_path)
            return DataMinInputSchema(df=data.df)
    
        @staticmethod
        def from_args(arguments: dict[str, Any]) -> "DataMinInputSchema":
            input_data_file_path = arguments["input_data_file_path"]
            return DataMinInputSchema.from_schema(input_data_file_path=input_data_file_path)
  • Registration of the 'data_min' tool in the MCP tools list, specifying name, description, and input schema.
    types.Tool(
        name=MCPServerDataWrangler.data_min.value[0],
        description=MCPServerDataWrangler.data_min.value[1],
        inputSchema=DataMinInputSchema.input_schema(),
    ),
  • Mapping of the 'data_min' tool name to its handler function in the dispatch dictionary.
    MCPServerDataWrangler.data_min.value[0]: handle_data_min,
  • Enum definition associating 'data_min' with its name and description.
    data_min = ("data_min", "Minimum values for each column")
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Minimum values for each column' implies a read-only statistical computation, but it doesn't specify whether this requires specific data formats, what happens with missing values, whether it modifies the input file, or what the output format looks like. For a data processing tool with zero annotation coverage, this is insufficient behavioral context.

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 extremely concise at just 5 words ('Minimum values for each column'). It's front-loaded with the core purpose and contains zero wasted words. Every word earns its place by conveying essential information about what the tool computes.

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 complexity of data processing operations and the lack of both annotations and output schema, the description is incomplete. It doesn't explain what format the minimum values are returned in, whether the operation handles different data types, what happens with non-numeric columns, or any error conditions. For a statistical computation tool with no structured metadata, the description should provide more complete context.

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%, with the single parameter 'input_data_file_path' clearly documented in the schema. The description doesn't add any parameter-specific information beyond what the schema already provides. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

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

Purpose4/5

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

The description 'Minimum values for each column' clearly states the tool's purpose as computing minimum values for data columns. It uses specific terminology ('minimum values', 'each column') that distinguishes it from siblings like data_max or data_mean. However, it doesn't explicitly mention what resource it operates on (data files), which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools performing different statistical operations (data_max, data_mean, data_median, etc.), there's no indication of when minimum values are appropriate versus other summary statistics. The description lacks any context about use cases or prerequisites.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shibuiwilliam/mcp-server-data-wrangler'

If you have feedback or need assistance with the MCP directory API, please join our Discord server