Skip to main content
Glama
optuna

Optuna MCP Server

Official
by optuna

plot_edf

Generate an EDF (Empirical Distribution Function) plot of optimization objective values as an image. Specify the target objective index and axis label.

Instructions

Return the EDF plot as an image.

    Args:
        target:
            An index to specify the value to display. To plot nth objective value, set this to n.
            Note that this is 0-indexed, i.e., to plot the first objective value, set this to 0.
        target_name:
            Target’s name to display on the axis label.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNo
target_nameNoObjective Value
Behavior2/5

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

With no annotations, the description should disclose behavioral traits, but it omits details such as return format (e.g., image type), side effects (none), and prerequisites (e.g., trials must exist).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively concise but contains a docstring format with repetitive parameter documentation. The main purpose is front-loaded.

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?

The tool lacks explanation of the return value (image format, resolution). Prerequisites like requiring a study with trials are not mentioned, making it less complete given no output schema.

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

Parameters4/5

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

The description adds significant value beyond the input schema by explaining that target is 0-indexed with examples, and that target_name is the axis label. This compensates for the 0% schema description coverage.

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 clearly states 'Return the EDF plot as an image' with a specific verb and resource. However, it does not distinguish from sibling plot tools like plot_contour or plot_optimization_history.

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?

No guidance is provided on when to use this tool versus alternatives. The description only details parameters without any context on prerequisites or typical use cases.

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/optuna/optuna-mcp'

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