Skip to main content
Glama

save_module

Copy an approved described schematic sheet and its library parts to a user's module shelf for reuse; reject sheets lacking required docs or ports without type/carries.

Instructions

Copy a described sheet and its library parts to the person's shelf of modules, after they approved the board. Refused without does or with a port that has no type and no carries (describe_sheet).

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": {
      "file": "<file>"
    },
    "name": "save_module"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
nameNo
replaceNo

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 the key behavioral traits: this is a write/copy operation into the user's module shelf and it can fail under two named invalid-input conditions. Left uncovered are permission requirements, whether an existing module is overwritten and how 'replace' interacts with that, and whether the copy is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and followed by failure conditions, so the shape is reasonable. However the wording is compressed to the point of obscurity ('without does', 'no carries'), trading clarity for brevity rather than earning conciseness.

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?

This is a mutation tool with no annotations, no output schema, and zero documented parameters, so the description must do nearly all the work. It covers the action and failure modes but omits parameter meaning, overwrite semantics, and return behavior — too many gaps for a three-parameter write operation.

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%, so the description needed to compensate and does not: none of the three parameters (file, name, replace) are mentioned, and there is no hint that 'file' identifies the described sheet or what 'replace' does. The only indirect signal is 'copy a described sheet', which loosely implies the source argument but is not tied to the schema.

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 does name a concrete verb and resource — copying a described sheet plus its library parts onto the user's module shelf — but the phrasing is heavy domain jargon ('does', 'carries', 'the person's shelf of modules') that an agent unfamiliar with this vocabulary may not decode reliably. It references describe_sheet as the source concept, which helps tie it to a sibling, but the core purpose lands as only roughly clear.

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?

It gives a precondition ('after they approved the board') and explicit failure conditions ('refused without does or with a port that has no type and no carries'), which is real usage context. It does not name an alternative tool or state when not to use this one beyond those refusal cases, so guidance is implied rather than complete.

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