Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Compare Templates

compare_templates
Read-onlyIdempotent

Compares two template files on disk to determine whether they are byte-identical and reports their size difference.

Instructions

Compare two template files on disk: whether they are byte-identical, and how their sizes differ.

Use it to tell whether two templates are the same file. It does not read the templates' settings, so it can't say which properties or dimensions differ. Needs: both files on disk. Read-only. Returns: comparison with file_1 and file_2 (size, modified time, SHA-256), identical and size_delta_bytes.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe two templates: `template1_path` and `template2_path`, both required.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive, so repeating "Read-only" adds little. The description goes beyond them by stating the prerequisite (both files must exist on disk) and describing the concrete output fields (size, modified time, SHA-256, identical, size_delta_bytes), which tells the agent exactly what evidence it will get. It doesn't mention behavior on missing files or how modified time is compared, so a small gap remains.

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 core comparison semantics, then usage, constraints, and return summary in short sentences. The trailing "Returns:" clause partially restates the output schema, which is the only mildly redundant element, but it's tight overall.

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

Completeness5/5

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

For a two-file read-only comparison tool with full schema coverage, annotations, and an output schema, the description covers purpose, prerequisites, limitations, and return shape. An agent has everything needed to call it correctly and interpret results.

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 both `template1_path`/`template2_path` are documented in the schema, so the baseline is 3. The description only reinforces that both files must be on disk; it adds no path format, relative-vs-absolute, or ordering semantics beyond the schema.

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 ("Compare two template files on disk") and immediately narrows what "compare" means here: byte-identity and size difference. The explicit disclaimer that it does not read template settings sharply bounds the purpose so an agent won't confuse it with a settings/dimension diff tool.

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?

"Use it to tell whether two templates are the same file" gives a clear use case, and "does not read the templates' settings, so it can't say which properties or dimensions differ" is an explicit when-not-to-use condition. It stops short of naming a concrete alternative tool for the settings-diff case, so it's a 4 rather than a 5.

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