Skip to main content
Glama

select_board

Choose the FPGA board for the current project; subsequent builds use its part number when no part is specified, and list_boards shows the active choice.

Instructions

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.

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": {
      "board_id": "<board_id>"
    },
    "name": "select_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
board_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 one important stateful behavior: this sets a default that `build` will use. However, it says nothing about whether the selection persists, what happens when `board_id` is invalid or the board is absent, or whether the call fails versus no-ops, leaving meaningful behavioral gaps for a state mutation.

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?

Two short sentences, front-loaded with the action and followed by the effect, with no filler. Minor ambiguity in phrasing such as "uses its part" costs it a top 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 one-parameter, no-output-schema tool this covers the essentials of what it does and why it matters downstream. It is incomplete on id provenance, error behavior, and selection persistence, which an agent would need before invoking it confidently.

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% and the single parameter `board_id` has no documentation in the schema, while the description never explains what a board id is, its format, or explicitly where to obtain one. The reference to `list_boards` for "the current choice" hints at a source for ids but does not state that the same values are valid inputs, so compensation for the coverage gap is thin.

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 and resource ("Select the board to work with") and states the downstream consequence that `build` consumes this choice, which distinguishes it from the listing sibling `list_boards`. It stops short of a full sibling differentiation (e.g., versus `detect_boards`), so it is clear but not maximally crisp.

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?

It provides real usage context: selection matters because `build` falls back to this board when no part is given, and the user can alternatively pick in the dashboard, with `list_boards` recommended to read the current choice. There is no explicit when-not condition or statement of what happens if a board is already selected, so it is clear context rather than full routing guidance.

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