Retrieve a complete list of materials defined in an Abaqus model by specifying model_name. Provides material inventory for simulation setup and verification.
List all materials in the specified model.
| Name | Required | Description | Default |
|---|---|---|---|
| timeout | No | ||
| model_name | No | Model-1 |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. The wording 'List all materials' implies a read-only operation and communicates scope, but it does not disclose expected behavior for missing models, empty results, timeouts, or any side effects. It is adequate but thin.
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, tightly scoped sentence with no wasted words. It front-loads the action and target, making it easy to parse quickly.
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?
For a simple listing tool with an output schema, the description does not need to explain return values. However, with no annotations and no usage guidance, it leaves the agent to infer behavior for optional parameters and model selection. It is minimally viable but not fully 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?
Schema description coverage is 0%, so the description must compensate. It partially clarifies model_name by saying 'specified model', but it does not explain the timeout parameter, defaults, or how the optional parameters behave. The description adds only minimal value beyond the schema's property names.
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 uses a specific verb ('List') with a clear resource ('all materials') and scope ('specified model'). It clearly distinguishes this tool from siblings like create_hyperelastic_material, list_elements, and list_jobs by naming both the action and target resource.
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. It does not mention better-suited sibling tools for material creation, model inspection, or other listing operations, and it provides no exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.