Skip to main content
Glama
Sign In
CAD-CAE-Agent SolidWorks MCP Server

CAD-CAE-Agent SolidWorks MCP Server

by caoguanqiu1-alt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_template_library

Browse and search the organization's template library to find available SOLIDWORKS templates. Use it to discover reusable models or study setups before starting CAD/CAE work.

Instructions

List available templates from the template library.

This tool provides browsing and searching capabilities for the organization's template library.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input_data": "<input_data>"
    },
    "name": "list_template_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe input data value.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden. It mentions 'browsing and searching capabilities' but fails to disclose behavioral traits such as read-only nature, required permissions, or output structure.

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?

The description is concise, using two sentences without extraneous information. However, its brevity sacrifices needed detail.

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

Completeness2/5

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

Despite having an output schema and many sibling tools, the description lacks completeness. It does not cover how browsing/searching works, what parameters to pass, or how it fits with other template-related tools.

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

Parameters1/5

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

The input schema has one generic object parameter 'input_data' with no structural details. The description does not explain what input_data should contain or how to use it, leaving the agent with no guidance.

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?

The description clearly states the verb 'List' and resource 'available templates from the template library', and mentions browsing and searching capabilities. It distinguishes from sibling tools like create_template and apply_template.

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?

The description implies usage for browsing/searching templates but does not provide explicit when-to-use or when-not-to-use guidance or compare with alternative tools like extract_template or compare_templates.

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