Skip to main content
Glama
ghostiee-11

holoviz-viz-mcp

by ghostiee-11

transform_data

Transform a dataset by applying operations such as filter, groupby, sort, or derive, saving the result as a new dataset.

Instructions

Transform a dataset using common operations. Saves the result as a new dataset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aggNoAggregation function for groupby — mean, sum, count, min, max, median, stdmean
limitNoLimit number of rows in output
valueNoFilter value or expression (e.g. '> 5', '== "setosa"', 'in ["A","B"]')
columnNoColumn to operate on (for filter/sort)
sort_byNoColumn to sort by
group_byNoColumn(s) to group by (comma-separated for multiple)
ascendingNoSort ascending (default True)
operationYesOne of 'filter', 'groupby', 'sort', 'derive', 'sample', 'drop_na', 'pivot'
expressionNoPython expression for derive (e.g. 'col_a * col_b')
new_columnNoName for derived column
output_nameNoName for the resulting dataset (auto-generated if not provided)
dataset_nameYesSource dataset name

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description must fully convey behavior. It only states that the result is saved as a new dataset, but omits details like side effects, performance considerations, or error handling.

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 with two short sentences. No redundant information, front-loaded with the main action.

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 complexity (12 parameters, 6 operations), the description is too minimal. It does not explain operation-specific details or output expectations, leaving gaps despite the output schema.

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?

Parameter descriptions in the schema are comprehensive (100% coverage). The description does not add extra meaning beyond the schema, so the baseline score of 3 is appropriate.

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 transforms a dataset, but it does not specify which operations are available, making it somewhat vague. It differentiates from siblings like 'merge_datasets' but is not precise about the scope.

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 such as 'analyze_data' or 'execute_code'. It lacks context for selection.

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

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/ghostiee-11/holoviz-viz-mcp'

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