Skip to main content
Glama

program

Load a bitstream onto an FPGA board with openFPGALoader, defaulting to a dry run and temporary SRAM; use write_flash for permanent storage.

Instructions

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.

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": {
      "bitstream": "<bitstream>"
    },
    "name": "program"
  }
}

Input Schema

NameRequiredDescriptionDefault
partNo
boardNo
cableNo
confirmNo
bitstreamYes
write_flashNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the safety burden well: it discloses that omitting confirm makes this a dry run that only prints the command, and that write_flash=true makes the design persistent while SRAM mode leaves the board's stored design untouched. It does not cover failure behavior, required board selection state, or what a successful run reports, so it falls short of fully transparent.

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?

Front-loads the core action and the safety-relevant dry-run rule early, which is the right ordering. Slight waste in the redundant pair of sentences about write_flash=true making the design persistent.

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 hardware-mutating tool with zero annotation coverage and no output schema, the description covers the highest-risk semantics (dry run, persistence) but leaves board/cable targeting unexplained and does not say how the tool reports results or what happens when no board is selected.

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 0% across 6 parameters, so the description must compensate. It meaningfully explains confirm, write_flash, and part, but board and cable receive no explanation anywhere, leaving half the hardware-targeting surface undocumented.

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

Purpose5/5

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

States a specific verb and resource ('Load a bitstream onto a board') plus the underlying mechanism (openFPGALoader), which is enough for an agent to distinguish this from build/simulate/detect_boards siblings.

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

Usage Guidelines4/5

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

Gives explicit mode-selection rules: prefer write_flash=false, use write_flash=true only on an explicit user request, and pass part to pre-validate device support. It stops short of saying when to call this versus adjacent tools (e.g. select_board or detect_boards first), so it is strong conditional guidance rather than full alternative routing.

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