Skip to main content
Glama

bom

Read-only

Generates a bill of materials for a circuit file, grouped by part, and checks whether the board is ready to order.

Instructions

Bill of materials for a circuit, grouped by part, and whether the board is ready to order.

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

Input Schema

NameRequiredDescriptionDefault
fileYesCircuit file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral content by describing the shape of the result (grouped by part, includes readiness), but says nothing about error handling, whether the file must be a project file, or how large/complex boards are handled.

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?

A single compact sentence with no filler, and the primary content (BOM grouped by part) is front-loaded before the secondary readiness signal. It reads as a noun phrase rather than a full statement of action, which costs it a perfect score 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 simple one-parameter read tool with full schema coverage, most of what an agent needs is present, and no output schema exists so the description does carry the burden of describing the return. It conveys the grouping and the readiness flag but not the response format or what fields each part entry holds.

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?

Only one parameter exists and schema coverage is 100%, so the schema already documents 'file' as the circuit file. The description adds no further meaning about the parameter (accepted formats, whether a path or circuit name is expected), which is acceptable but no better than the baseline when the schema does the work.

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 names a concrete resource (bill of materials for a circuit) and adds distinguishing content: grouping by part and an order-readiness check. It is not a tautology of the name, and the 'ready to order' element separates it from summary-style siblings like circuit_summary or copper_summary, though it never names an alternative explicitly.

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 when-to-use guidance, no prerequisites (e.g. circuit must be open or file must exist), and no statement of when to prefer this over export_fabrication or board_summary. The order-readiness angle hints at a pre-fabrication check, but that is inference rather than stated guidance.

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