Skip to main content
Glama
Sign In
McuBuddy

McuBuddy

by cunjun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

configure_elf

Specify the ELF or AXF file path to enable symbol resolution during MCU debugging. This allows the debugger to map addresses to function names for accurate fault diagnosis.

Instructions

Set the ELF/AXF file path for symbol resolution.

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": {
      "elf_path": "<elf_path>"
    },
    "name": "configure_elf"
  }
}

Input Schema

NameRequiredDescriptionDefault
elf_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.2

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only states the action, not whether the setting persists, affects other commands, validates the path, or overwrites previous values. This leaves important behavioral traits undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that directly states the tool's purpose. It contains no redundant information and is well-structured for quick understanding.

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 simple one-parameter setter with no output schema and no annotations, the description provides sufficient purpose and parameter context, but it lacks usage guidelines and behavioral side effects. It is adequate but not comprehensive, leaving gaps that an agent would need to infer.

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?

The schema has zero description coverage for the one parameter. The description adds context by mentioning that the path can be ELF or AXF and is for symbol resolution, but it does not explain the expected format, path rules, or how the parameter value is used beyond the schema's property name.

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 clearly states the action ('Set') and the specific resource ('ELF/AXF file path') and purpose ('for symbol resolution'). It distinguishes from sibling tools like configure_probe, configure_log, and configure_keil_project by specifying the exact file type and role.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, contexts, or when not to use it. The purpose implies usage, but without explicit exclusions or alternative references, the guidance is absent.

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

Deploy Server

Other Tools