Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

copy_file

Copies a SOLIDWORKS file to a new path while keeping its extension, blocking overwrites of existing targets and copies of files open with unsaved changes.

Instructions

Copy a file to a new path, keeping the extension. Refused when the target exists (unless overwrite), when the source is open with unsaved changes, when the target is open, and for protected folders. Files that reference the source keep pointing at the source.

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": {
      "source": "<source>",
      "target": "<target>"
    },
    "name": "copy_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesFull path of the file to copy
targetYesFull path of the copy (same extension; a missing folder is created)
overwriteNoReplace an existing target

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?

With no annotations supplied, the description carries the full disclosure burden and does so well: it names the four refusal preconditions, the overwrite escape hatch, and the non-obvious side effect that referencing files continue to point at the source rather than the copy. What is missing is the return value shape and any permission/scale caveats, which leaves a modest gap for a mutation tool with no output schema.

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 the core action and followed by the failure conditions in a tight parallel list. Every clause conveys a distinct constraint; nothing is padding.

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 three-parameter mutation with no annotations and no output schema, the description covers purpose, preconditions, and the reference-integrity side effect. The only shortfall is that an agent cannot learn what a successful call returns, which the absent output schema would otherwise have to supply.

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 description coverage is 100%, so all three parameters are already documented, including the extension rule and the missing-folder behavior. The description's mention of "keeping the extension" and "unless overwrite" largely restates the schema rather than adding syntax, format, or edge-case meaning beyond it, so the baseline of 3 applies.

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 ("Copy a file to a new path") plus the key invariant ("keeping the extension"). No sibling in the catalog performs file copying, so there is nothing to confuse it with, and the intent is unambiguous from the first clause.

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?

Enumerates the exact conditions under which the call is refused (existing target without overwrite, source open with unsaved changes, target open, protected folders), which tells an agent when the tool will fail before it calls it. It does not route to any alternative operation (e.g., move or rename), but no such sibling is established, so the guidance is otherwise complete for the call decision.

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