Retrieve the names of all optimization studies stored in the database.
Get all study names from the storage.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.2.0Output schema / (root)Previous value: -nullNew value: +{
+ "$defs": {
+ "StudyResponse": {
+ "properties": {
+ "directions": {
+ "anyOf": [
+ {
+ "items": {
+ "enum": [
+ "minimize",
+ "maximize"
+ ],
+ "type": "string"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "The optimization directions for each objective.",
+ "title": "Directions"
+ },
+ "metric_names": {
+ "anyOf": [
+ {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "The metric names for each objective.",
+ "title": "Metric Names"
+ },
+ "sampler_name": {
+ "anyOf": [
+ {
+ "enum": [
+ "TPESampler",
+ "NSGAIISampler",
+ "RandomSampler",
+ "GPSampler"
+ ],
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "The name of the sampler used in the study.",
+ "title": "Sampler Name"
+ },
+ "study_name": {
+ "title": "Study Name",
+ "type": "string"
+ }
+ },
+ "required": [
+ "study_name"
+ ],
+ "title": "StudyResponse",
+ "type": "object"
+ }
+ },
+ "properties": {
+ "result": {
+ "items": {
+ "$ref": "#/$defs/StudyResponse"
+ },
+ "title": "Result",
+ "type": "array"
+ }
+ },
+ "required": [
+ "result"
+ ],
+ "title": "get_all_study_namesOutput",
+ "type": "object"
+}v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It only states 'from the storage' without clarifying whether it is read-only, requires authentication, or has side effects. The agent cannot infer safety or permission requirements.
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?
The description is a single, concise sentence that efficiently conveys the tool's purpose. It is appropriately front-loaded and contains no superfluous words, though it could be slightly more descriptive without losing conciseness.
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 the absence of annotations and parameters, the description is minimally viable. The output schema exists, so return value explanation is not required, but the tool context (e.g., relationship to studies, effects of previous commands) is omitted. It is adequate but has clear gaps.
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?
The input schema has no parameters and 100% coverage, so the description adds no parameter details. The phrase 'from the storage' is implied by the schema's empty object. With zero parameters, the baseline is 4, but the description adds no value, resulting in a 3.
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?
The description 'Get all study names from the storage' clearly states the action (get) and resource (study names). It is specific and distinguishes from other sibling tools that retrieve different entities like metrics or directions, though it could explicitly differentiate itself.
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?
The description offers no guidance on when to use this tool versus alternatives like 'get_metric_names' or 'get_directions'. It does not mention prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.