Skip to main content
Glama

plot_scatter

Generate scatter plots to visualize relationships between variables, with options to map point sizes and colors to additional data dimensions for multi-dimensional analysis.

Instructions

Create a scatter plot with optional size and color mapping.

This tool generates a scatter plot where point sizes and colors can represent additional data dimensions.

Args: x: X-axis data. Column name (string) if using data file, or list of values. y: Y-axis data. Column name (string) if using data file, or list of values. data_input: Optional. {"file_path": "path/to/file.csv"} or {"data": {...}} size: Optional point sizes. Column name, list of values, or single value. color: Optional point colors. Column name or list of values for colormap. style: Optional. {"title": "...", "xlabel": "...", "ylabel": "...", "colormap": "viridis", "grid": True} output: Optional. {"format": "png/pdf/svg", "width": 15, "height": 10, "dpi": 300}

Returns: PIL Image object or bytes containing the plot

Examples: Basic scatter plot: >>> plot_scatter(x=[1, 2, 3], y=[1, 4, 9])

Scatter with size and color mapping:
>>> plot_scatter(
...     x="height",
...     y="weight",
...     size="age",
...     color="bmi",
...     data_input={"file_path": "health_data.csv"},
...     style={"colormap": "plasma"}
... )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYes
yYes
data_inputNo
sizeNo
colorNo
styleNo
outputNo
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by explaining what the tool returns ('PIL Image object or bytes containing the plot'), providing comprehensive examples, and describing the optional nature of most parameters. It doesn't mention performance characteristics, error conditions, or memory usage, but covers the core behavioral aspects adequately.

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 well-structured with clear sections (purpose, args, returns, examples) and front-loaded information. It's appropriately sized for a complex tool with 7 parameters, though the examples section is quite detailed. Every sentence adds value, but some redundancy exists between the parameter descriptions and examples.

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

Completeness4/5

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

For a complex 7-parameter tool with no annotations and no output schema, the description provides comprehensive coverage including purpose, parameter semantics, return values, and examples. The main gap is lack of explicit guidance on when to use versus sibling plotting tools, but otherwise it's quite complete for enabling correct tool invocation.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by providing detailed parameter explanations in the 'Args' section, including data types, usage patterns, and examples for all 7 parameters. It clarifies that x and y can be column names or lists, explains the structure of data_input, size, color, style, and output objects with specific examples.

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 clearly states the tool's purpose: 'Create a scatter plot with optional size and color mapping.' It specifies the verb ('create'), resource ('scatter plot'), and distinguishes from siblings by mentioning size/color mapping capabilities that differentiate it from basic plotting tools like plot_line or plot_bar.

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

Usage Guidelines3/5

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

The description implies usage through examples showing basic vs. enhanced scatter plots, but doesn't explicitly state when to use this tool versus alternatives like plot_line or plot_heatmap. The examples provide some context but lack explicit guidance about choosing between different plotting tools for different data visualization needs.

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/nishide-dev/ml-research-mcp'

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