Get time step indices and corresponding values from a COMSOL dataset for time-dependent study results.
Get inner solution indices and values (time steps in time-dependent study).
Args: dataset: Dataset name (default: default dataset) model_name: Model name (default: current model)
Returns: Arrays of indices and corresponding values (e.g., time values)
| Name | Required | Description | Default |
|---|---|---|---|
| dataset | No | ||
| model_name | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states the tool returns arrays but does not disclose any behavioral traits such as mutability, permissions, or side effects. For a read operation, this is a minor gap.
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 extremely concise: two short paragraphs with front-loaded purpose, then Args and Returns. No wasted sentences.
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 no output schema and no annotations, the description adequately explains the tool's purpose, parameters, and return type. It could benefit from a brief example or more detail on the return format, but is largely complete.
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 description adds meaning to both parameters (dataset and model_name) by indicating their defaults and roles, which the input schema alone does not provide. Schema coverage is 0%, so the description fully compensates.
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 explicitly states the verb 'Get' and the resource 'inner solution indices and values', with context 'time steps in time-dependent study'. This clearly distinguishes it from sibling tools like results_outer_values and results_global_evaluate.
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 implies usage for time-dependent studies by mentioning 'time steps', but it provides no explicit when-to-use or when-not-to-use guidance, nor does it compare to alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.