Skip to main content
Glama
solidworks-mcp

solidworks-mcp

sw_check_printability

Checks whether the current SOLIDWORKS model is suitable for 0.4 mm nozzle FDM printing and returns hard guardrail warnings for printability issues.

Instructions

检查当前模型是否适合 0.4 喷嘴 FDM 打印,返回硬护栏告警。

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": "sw_check_printability"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose the return character ('returns hard guardrail warnings'), which usefully signals a pass/fail gate rather than a data query. But it never states whether the tool mutates the model, what conditions trigger warnings, or whether warnings are blocking.

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

Conciseness4/5

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

A single front-loaded sentence with no filler, opening with the verb and the print constraint. It is efficient, though it is terse enough that a second short clause on outcome semantics would have cost little.

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

Completeness3/5

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

With no annotations, no output schema, and an empty parameter object, the description is the only source of behavioral detail, and it covers just one line. It leaves open what the guardrails check, what a warning result looks like, and whether the operation is read-only, which matters for a validation gate.

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?

The tool takes zero parameters and the schema is an empty object, so there is no parameter meaning to add; the baseline of 4 applies. The description correctly implies the tool operates on implicit 'current model' state rather than on arguments, which matches the schema.

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

Purpose4/5

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

The description states a specific verb and resource: checking whether the current model is suitable for 0.4-nozzle FDM printing. That is far more precise than a tautology. It does not, however, distinguish this check from adjacent siblings such as sw_export_stl or sw_open_in_bambu, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is a pre-print or pre-export validation step, but the description never says when to call it, whether it must be run before exporting or printing, or what to do instead if it fails. No exclusions or alternatives are named.

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