Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Build, inspect, simulate and program FPGA designs. Call list_backends and list_boards first. build starts a background job and returns a job_id; poll build_status until state is 'done' or 'failed'. program writes to hardware only when confirm=true. Installing an add-on needs the user's approval: call request_install, tell the user to open the dashboard, then poll install_status. Only the user can approve, in the dashboard. If a request is rejected, stop: do not retry it or work around it.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_backendsA

List the installed and planned FPGA add-ons, the part families each covers, and its state.

list_boardsA

List known boards (part, add-on, programmer support) and the one currently selected.

select_boardB

Select the board to work with. build then uses its part when no part is given.

The user can also pick the board in the dashboard; check list_boards for the current choice.

dashboard_infoA

Return the address of the local status window and whether it is running.

request_installA

Ask the user to approve installing an add-on. Nothing is downloaded by this call.

The request appears in the dashboard with what would be installed, from where, the disk cost and the licence situation. Only the user can approve or reject it there. reason: one sentence for the user on why you need it.

request_uninstallB

Ask the user to approve removing an add-on that Brigse installed. Nothing is deleted by this call.

Only add-ons installed by Brigse can be removed (the downloaded open-source tools); vendor tools the user installed are never touched. Poll install_status with the returned request_id.

install_statusB

Check an install or uninstall request. If the user approved it, start the work (when automatic).

wait_seconds: wait up to this long (max 50) for the user's decision.

activityA

What is in progress right now (builds, installs, programmer use) and who started it.

The user can also start actions from the dashboard, so check this before starting work that needs the same add-on or the programmer.

backend_controlA

Start, stop or check an add-on's runtime (for ise_spartan3: its VM).

action: 'start', 'stop' or 'status'. Stopping frees RAM; it is refused while a build runs.

buildA

Start a full build (synthesis to bitstream) as a background job.

project_dir: folder with the HDL sources (copied to the build machine; old outputs are skipped). top: top module name. If .xst exists in the folder, the project's own synthesis script is used. part: device-package-speed, e.g. xc3s700a-fg484-4. Defaults to the selected board's part. The part selects the add-on. sources: paths relative to project_dir; default is every .v/.vhd in the folder except testbenches. constraints: constraints file relative to project_dir; default is the only .ucf (ISE) or .cst (Gowin) in the folder. backend: force a specific add-on. By default the usable add-on with the highest priority is used (the vendor tool when the user has it, otherwise the open-source flow).

build_statusA

Report a build job's progress; when it has finished, fetch the outputs and return the report.

wait_seconds: wait up to this long (max 50) for the job to finish before answering.

reportC

Summarise the reports in a build output folder: utilisation, timing, failing constraints, bitstream.

backend: the add-on that produced the folder; detected automatically when omitted.

simulateB

Compile and run a Verilog testbench with Icarus Verilog.

sources: files relative to cwd, testbench included. top: testbench module, if ambiguous. The run passes when the simulator exits 0 and prints no FAIL/ERROR text.

detect_boardsC

List connected USB programming probes and, for a given cable, the FPGAs on its JTAG chain.

programA

Load a bitstream onto a board with openFPGALoader.

Prefer the temporary SRAM load (write_flash=false): it leaves the design stored on the board untouched. Use write_flash=true only when the user explicitly asks for a permanent write.

Without confirm=true this is a dry run that only shows the command. write_flash=true makes the design persistent. Pass part to check first that the loader supports the device.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 15 tools

Disambiguation4/5

Most tools map to a distinct resource+action: listing backends vs. boards vs. probes, installing vs. running a backend, building vs. simulating vs. programming. The closest overlaps are list_boards vs. detect_boards (known boards vs. connected JTAG hardware) and backend_control/install_status, but the descriptions make those boundaries clear.

Naming Consistency4/5

The dominant pattern is verb_noun or noun_noun with underscores (list_backends, select_board, request_install, build_status, detect_boards). A few bare names (build, report, simulate, activity, dashboard_info) deviate slightly but remain unambiguous and readable.

Tool Count5/5

15 tools sit at the top of the well-scoped range and each covers a real step in the FPGA workflow: discovery, install approval, backend lifecycle, build, status/report, simulation, and programming. No tool looks redundant or tacked on.

Completeness4/5

The surface covers the full lifecycle from hardware discovery through install, build, report, simulation, and bitstream loading, with no obvious dead ends. Minor gaps exist: no cancel/abort for a running build, no listing or cleaning of build outputs, and no tool to inspect source/constraint files before building.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues