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

dbgprobe-mcp-server

by es617
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

dbgprobe.svd.list_registers

List all registers of a specified peripheral to inspect memory-mapped register details during embedded debugging.

Instructions

List all registers for a peripheral.

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>"
    },
    "name": "dbgprobe.svd.list_registers"
  }
}

Input Schema

NameRequiredDescriptionDefault
peripheralYesPeripheral name (e.g. 'GPIO').
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 only states the action, with no mention of side effects, permissions, or behavior beyond listing.

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?

Single sentence, no wasted words. Efficiently conveys the core purpose.

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?

With no output schema and minimal description, the tool lacks details about return format or any prerequisites. Adequate for a simple list operation but could be enriched.

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 coverage is 50% (session_id lacks description). The tool description adds no extra meaning beyond the parameter description for 'peripheral', and provides no context for 'session_id'.

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 verb 'List' and the resource 'registers for a peripheral', which is specific and distinguishes from sibling tools like list_fields and list_peripherals.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. The description implies it's for listing all registers of a peripheral, but does not provide when-not-to-use or name alternatives.

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