Skip to main content
Glama

export_package

Exports a folder containing BOM, local datasheets, and library-part verification status for a circuit file to support design review and handoff.

Instructions

Write a folder with the BOM, local datasheets and the library parts' verification status.

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

Input Schema

NameRequiredDescriptionDefault
fileYesCircuit file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden. It implies a file-system write ('Write a folder') but does not disclose where the folder is created, whether an existing folder is overwritten, what permissions are required, or what happens on failure. Listing the contents is useful but far from a complete behavioral profile for a mutating export tool.

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?

The description is a single, front-loaded sentence with no wasted words. The verb and the produced artifact are immediately clear.

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?

For a write-oriented export tool with no annotations and no output schema, the description is missing critical context: output location, overwrite behavior, and expected side effects. An agent could invoke it, but with significant uncertainty about what will happen on disk.

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% with a single parameter ('file' → 'Circuit file'), so the schema already documents the parameter's meaning. The description adds no additional parameter context, such as whether 'file' is the only input and where the output folder destination comes from, which is consistent with the baseline 3 when the schema does the heavy lifting.

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?

The description gives a specific verb ('Write a folder') and enumerates the folder's contents (BOM, local datasheets, library parts' verification status), which distinguishes it from a plain BOM export. However, it does not explicitly differentiate itself from siblings such as export_fabrication or export_html, leaving the agent to infer the package boundary.

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 no guidance on when to use this tool versus bom, export_fabrication, or other export siblings. The agent must guess from the name and context whether this is the right export choice for a given workflow.

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