Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Template Library

list_template_library
Read-onlyIdempotent

Lists templates from the shared template library using optional filters for inspection; currently returns a not_supported error until an adapter is implemented.

Instructions

List the templates in the shared template library.

Not available yet: no adapter implements it, so every call returns an error with error_type: "not_supported". It is planned for a future release. Read-only. Returns: once available, the library's templates under data.

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_dataYesA mapping of optional filters; none is required.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / properties / input_data / description
      Previous value: -"The input data value."New value: +"A mapping of optional filters; none is required."
  2. First observedv1.0.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses the decisive behavior: the tool is a unimplemented stub that fails on every call with a specific error_type. That is exactly the kind of context annotations cannot carry, and it is not contradicted by readOnlyHint since failing reads mutate nothing.

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?

Front-loaded with the purpose, then the unavailability caveat, then return shape; nothing is buried. 'It is planned for a future release' partly restates the stub warning, and the Returns line duplicates the existing output schema, so it is slightly longer than strictly needed.

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 one-parameter tool with an output schema and full annotation coverage, the definition supplies what matters most: that it cannot succeed today. The only meaningful gap is the absence of a pointer to the tool an agent should use instead for listing templates.

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

Parameters3/5

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

Schema coverage is 100% and the single input_data parameter is already documented as an optional filter mapping, so the schema does the work. The description says nothing about which filters exist or how they are applied, adding no meaning beyond 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?

States a specific verb and resource: 'List the templates in the shared template library.' That distinguishes it from write-side siblings such as save_to_template_library or create_template, though the description never names an alternative explicitly.

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?

Gives unusually strong when-NOT guidance: 'no adapter implements it, so every call returns an error with error_type: not_supported', which tells an agent to avoid this tool entirely. It stops short of pointing to what an agent should use instead to enumerate 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