List all studies in a COMSOL model and view their types. Use it to inspect simulation study configurations before running multiphysics analyses.
List all studies in a model.
Args: model_name: Model name (default: current model)
Returns: List of study names with their types
| Name | Required | Description | Default |
|---|---|---|---|
| model_name | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the default behavior (current model if model_name omitted) and the return format (list of names with types). This is adequate for a simple list operation, though it could mention error handling or model existence.
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 brief and front-loaded with the purpose, followed by parameter and return details. It is efficient, though it partly repeats the schema's default value. No wordiness, but could be slightly more streamlined.
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 tool's simplicity (one optional parameter, no output schema), the description covers the key aspects: what it lists, how to specify the model, and what the response contains. It is complete for its complexity level.
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 0% description coverage for the parameter. The description adds value by stating 'Model name (default: current model)', which clarifies the parameter's meaning and default behavior beyond the schema's type definition.
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 clearly states 'List all studies in a model' using a specific verb (list) and resource (studies) in context. This distinguishes it from sibling tools like study_solve or study_cancel, which perform different actions.
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 does not provide explicit guidance on when to use this tool versus alternatives like study_solve or study_get_progress. While it is clear what it does, it offers no context for selection or exclusion of sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.