Skip to main content
Glama

use_module

Copies a module's sheet and any missing parts next to the circuit file, then adds an instance for reuse in a Copperflow PCB project.

Instructions

Copy a module's sheet (and parts the project lacks) beside the circuit file; then add_instance. A library's sheet must be plain; its parts come as 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": {
      "module": "<module>",
      "file": "<file>"
    },
    "name": "use_module"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
moduleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: files are copied next to the circuit file, missing parts are brought in, and a subsequent add_instance call is required. It omits what happens on conflicts (existing sheet or part), permissions, and failure modes, which matters for an operation that writes files.

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?

Two tight sentences with the action front-loaded and no filler. The terseness borders on telegraphic ('its parts come as data'), but nothing is wasted.

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?

For a writing, multi-step operation with no annotations, no output schema, and zero parameter documentation, the description should say more about side effects and error conditions. It does cover the copy-then-add_instance sequence and the library-sheet constraint, which is the minimum an agent needs to attempt the call.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, so the description must compensate, and it only weakly does. 'Beside the circuit file' hints that file is the circuit target and 'a module's sheet' hints module is the module identifier, but neither parameter is explicitly explained and no format or path expectations are given.

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

Purpose3/5

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

The description names a concrete action (copy a module's sheet plus missing parts beside the circuit file) and implies a follow-up step (add_instance), which is more specific than the bare name. However, it never states plainly that this instantiates/uses a module in the current circuit, and the jargon ('plain' sheet, 'parts come as data') leaves the core purpose only partly legible to an agent. It does hint at a distinction from save_module/module_info by describing a copy-and-instantiate flow, but does not name any sibling.

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

Usage Guidelines2/5

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

There is an implicit workflow cue ('then add_instance') and one usage constraint (a library's sheet must be plain), but no explicit when-to-use versus module_info, save_module, or import_part. The agent is left to infer prerequisites and exclusions on its own.

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