Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

list_materials

Lists SOLIDWORKS material categories, or material names and densities by search term or category, helping you identify available materials for a model.

Instructions

List materials from the SolidWorks material databases. With no input it returns the categories; give search (part of a name, e.g. '6061', 'ABS') or category (e.g. 'Steel', 'Plastics') to get material names and densities.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_materials"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoOnly materials whose name contains this text
categoryNoOnly this category, e.g. 'Aluminium Alloys'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the burden and does disclose the two distinct response shapes (category list vs. material names with densities), which is the key behavioral surprise. It implies read-only via 'List' but does not state whether `search` and `category` are ANDed together, nor anything about casing or matching behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose and then the branching behavior. Every clause carries information — the default no-input case and both filter parameters with examples — with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-optional-parameter read tool with no output schema, the description covers purpose, both modes, and roughly what is returned. The only meaningful gap is whether the filters combine conjunctively and whether matching is case-sensitive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds concrete value with real example values ('6061', 'ABS' for search; 'Steel', 'Plastics' for category) that illustrate expected granularity and naming conventions. It stops short of saying how the two filters interact when both are supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'List materials from the SolidWorks material databases' — which is immediately distinguishable from the geometry/feature/drawing list_* siblings. An agent knows what domain this operates on without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the two calling modes clearly: no input returns categories, and either `search` or `category` narrows to material names and densities. That effectively documents a browse-then-filter workflow. No alternatives are named, but there is no obvious sibling competing for this job.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools