Skip to main content
Glama
Sign In
stmctl-mcp

stmctl-mcp

by Sathvik-smarttrak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

stm32_raw_cli

Execute raw STM32_Programmer_CLI commands with custom arguments for advanced, low-level operations not covered by standard tools.

Instructions

Run raw parameters directly against STM32_Programmer_CLI for advanced/custom operations.

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": {
      "args": "<args>"
    },
    "name": "stm32_raw_cli"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsYesArray of command line argument strings (e.g. ['-c', 'port=SWD', '-e', 'all'])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states parameters are run 'directly', hinting at a raw passthrough without validation, but it fails to disclose potential risks, error behaviors, or the fact that invalid arguments could have serious consequences on the target device. This is notably insufficient for a raw CLI passthrough tool.

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 a single, focused sentence that front-loads the verb and resource. It is appropriately concise for a simple passthrough tool, though it could benefit from a brief caution or pointer to the underlying CLI's documentation. Overall, it is well-structured with no wasted words.

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?

Given the single parameter and high schema coverage, the description is adequate for a basic understanding. However, it lacks context about the underlying STM32_Programmer_CLI, potential risks, or when to prefer this over sibling tools. Since there is no output schema and no annotations, the description should provide more safety context to be fully complete for an AI agent.

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

Parameters4/5

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

The schema already describes the 'args' array with an example, providing high coverage. The description adds value by emphasizing that parameters are passed 'directly' and 'raw', clarifying that no transformation or validation occurs. This semantic nuance is important for the agent to understand the tool's behavior and complements the schema well.

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 tool runs raw parameters against STM32_Programmer_CLI, distinguishing it from the high-level sibling tools. It specifies the verb 'run' and the resource 'STM32_Programmer_CLI', making the purpose unambiguous and differentiating it as a low-level escape hatch.

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?

The phrase 'for advanced/custom operations' implies when to use it (when standard sibling tools don't suffice), but it doesn't explicitly mention alternatives or exclusions. There's no explicit statement like 'use when other tools do not cover the needed operation', so usage context is implied rather than clearly delineated.

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