Skip to main content
Glama
Sign In
McuBuddy

McuBuddy

by cunjun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

match_chip_name

Convert a chip alias into the exact target name expected by a debug backend, ensuring the correct device is selected for debugging.

Instructions

Resolve a chip alias to a backend-specific target name.

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": {
      "target": "<target>"
    },
    "name": "match_chip_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
backendNopyocd

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.2

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It implies a read-only lookup but does not explicitly state safety, side effects, error behavior (e.g., unmapped alias), or whether it modifies anything. The single sentence lacks context beyond the basic operation.

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, front-loaded sentence that efficiently communicates the core purpose. No filler or redundant information, earning a 5.

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

Completeness2/5

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

Given 2 parameters, no output schema, and no annotations, the description is too sparse to be complete. It lacks guidance on when to use, return format, error cases, and parameter semantics. For a simple lookup tool, this is below the minimum viable bar, though the core purpose is clear.

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 description only partially compensates. It implies that 'target' is the chip alias and 'backend' influences the resulting name, but it does not provide per-parameter details, accepted values, or format expectations. The description gives general semantics but not enough to fully understand the parameters.

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 uses a specific verb 'resolve' and clearly states the input (chip alias) and output (backend-specific target name). It distinguishes from siblings like get_target_info by focusing on alias resolution to a backend-specific name rather than general target information.

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?

The description does not explicitly state when to use this tool versus alternatives like get_target_info or configure_probe. There is no mention of exclusions, prerequisites, or scenarios where this tool is preferred. Only the basic function is described.

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