Skip to main content
Glama

connect

Open a debug session to a connected probe by specifying probe serial, target type, board ID, or custom board config.

Instructions

Open a debug session to a connected probe.

Args:
    unique_id: Whole or partial probe serial/unique ID to select a specific
        probe. Omit when exactly one probe is attached. Defaults to the
        ``PYOCD_PROBE_UID`` environment variable if unset.
    target: Target type override, e.g. "stm32f407vg" or "nrf52833". Takes
        precedence over a board config. Omit to use the selected board's
        target (when ``board_id`` is given), else the ``PYOCD_TARGET``
        environment variable, else pyOCD auto-detection.
    board_id: Load facts from ``boards/<board_id>.yaml`` through the shared
        board-config loader — pyOCD target, recover policy, silicon id, baud.
        Lets a custom ST/nRF board connect by id with no hand-passed target;
        call ``get_board_info`` to see the loaded facts. Defaults to the
        ``PYOCD_BOARD_ID`` environment variable.
    board_config: Path to an extra board-config file outside the tracked
        ``boards/`` directory, for a custom board. Defaults to the
        ``PYOCD_BOARD_CONFIG`` environment variable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNo
board_idNo
unique_idNo
board_configNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description must disclose behavior. It mentions opening a session and using environment variables, but does not explain what happens if already connected, permission requirements, or the state of the target after connection (e.g., halted). This leaves gaps in behavioral understanding.

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?

The description is well-structured with a lead sentence followed by concise parameter bullet points. While slightly lengthy, every sentence serves a purpose. The front-loading of the purpose is effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers parameter usage well and references environment variables, but does not discuss the return value (though output schema exists) or the resulting debugging state (e.g., halted target). This leaves some contextual gaps for a tool that initiates a session.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries full burden. It excellently explains each parameter: unique_id (partial match, env var), target (type override, precedence), board_id (YAML loading, env var), board_config (custom path). This adds substantial meaning beyond the schema.

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?

The description explicitly states 'Open a debug session to a connected probe,' which uses a specific verb and resource. It clearly distinguishes from sibling tools like 'disconnect' and 'flash_firmware', which handle different operations.

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?

The description provides clear context on when to omit parameters (e.g., 'Omit when exactly one probe is attached'), but does not explicitly discuss when not to use this tool or compare it to alternatives. It implicitly establishes connect as the first step before other debug actions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JasonPeng2019/BYO-Firmware-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server