Skip to main content
Glama

detect_boards

Lists connected USB programming probes and identifies FPGAs on a specified cable’s JTAG chain, helping you select and verify targets before programming.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "detect_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault
cableNo

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?

With no annotations, the description carries the full behavioral burden, yet it says nothing about whether the scan probes hardware actively, how long discovery takes, what permissions or drivers are needed, or what happens on failure. Only the broad shape of the result is implied.

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?

One compact sentence with the primary action front-loaded and the conditional cable behavior following. Nothing is wasted, though the compressed two-mode phrasing takes a second read to parse.

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 single-parameter read tool with no output schema and no annotations, the description covers intent but leaves the two operating modes ambiguous: is the probe list always returned, and is the JTAG enumeration purely additive? Return shape and hardware/error behavior remain unstated.

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 coverage is 0% and 'cable' is nullable with a null default, but the description partly compensates by explaining that supplying a cable yields the FPGAs on that cable's JTAG chain. It still does not say what identifier format 'cable' expects (name, serial, index) or what the null default does beyond listing probes.

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?

States a concrete verb and resources: 'List connected USB programming probes' and, conditioned on a cable, 'the FPGAs on its JTAG chain.' An agent knows what it reads. It does not, however, distinguish itself from the sibling 'list_boards', which sounds like it may overlap, and the name 'detect_boards' does not match the 'list probes' framing.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. The agent must guess whether to call detect_boards or list_boards/select_board for a given discovery task.

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