Retrieve trials on the Pareto front of a study to identify optimal trade-offs between multiple objectives.
Return trials located at the Pareto front in the study.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.2.0Output schema / (root)Previous value: -nullNew value: +{
+ "$defs": {
+ "TrialResponse": {
+ "properties": {
+ "params": {
+ "anyOf": [
+ {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "The parameter values suggested by the trial.",
+ "title": "Params"
+ },
+ "system_attrs": {
+ "anyOf": [
+ {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "System-defined attributes for the trial.",
+ "title": "System Attrs"
+ },
+ "trial_number": {
+ "title": "Trial Number",
+ "type": "integer"
+ },
+ "user_attrs": {
+ "anyOf": [
+ {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "User-defined attributes for the trial.",
+ "title": "User Attrs"
+ },
+ "values": {
+ "anyOf": [
+ {
+ "items": {
+ "type": "number"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "The objective values of the trial.",
+ "title": "Values"
+ }
+ },
+ "required": [
+ "trial_number"
+ ],
+ "title": "TrialResponse",
+ "type": "object"
+ }
+ },
+ "properties": {
+ "result": {
+ "items": {
+ "$ref": "#/$defs/TrialResponse"
+ },
+ "title": "Result",
+ "type": "array"
+ }
+ },
+ "required": [
+ "result"
+ ],
+ "title": "best_trialsOutput",
+ "type": "object"
+}v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description only states the function. It does not disclose behavioral traits like read-only nature or potential performance implications, though it is not misleading.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence of 8 words with no wasted content. Very concise and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and the presence of an output schema, the description is largely complete. It could mention relation to 'best_trial', but not strictly required.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has 0 parameters with 100% coverage; description adds no parameter info, but baseline for 0 params is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it returns trials at the Pareto front, using a specific verb and resource that distinguishes it from sibling tools like 'best_trial' (singular) and 'get_trials' (all trials).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives such as 'best_trial' or 'get_trials'. The description 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.
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