Skip to main content
Glama
Sign In
dbgprobe-mcp-server

dbgprobe-mcp-server

by es617
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

dbgprobe.svd.list_fields

Retrieve all bit fields defined for a specific register within a peripheral, using SVD data from the debug probe session.

Instructions

List all fields for a register.

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": {
      "session_id": "<session_id>",
      "peripheral": "<peripheral>",
      "register": "<register>"
    },
    "name": "dbgprobe.svd.list_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
registerYesRegister name (e.g. 'PIN_CNF[3]', 'OUT').
peripheralYesPeripheral name (e.g. 'GPIO').
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

The description does not disclose any behavioral traits such as side effects, whether it is read-only, or if it requires an active connection. With no annotations, this is insufficient for safe usage.

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 function with no unnecessary words. It is front-loaded and efficient.

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?

The description lacks critical context: no output format, no error conditions, no prerequisites (e.g., must be connected, peripheral/register must exist). For a tool with 3 required parameters and no output schema or annotations, this is incomplete.

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?

The tool description adds no additional meaning to the parameters beyond what the input schema already provides. Schema coverage is 67% (register and peripheral have descriptions, session_id lacks), but the description does not clarify the 'fields' output format or any constraints.

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 ('List all fields') and the resource ('for a register'), distinguishing it from sibling tools like 'list_peripherals' or 'list_registers'.

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 guidance is provided on when to use this tool, prerequisites (e.g., peripheral and register must exist), or comparison with alternatives like 'svd.read' or 'svd.set_field'.

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