embedded-mcp

Overview Schema Source Related Servers Discussions Admin

firmware_notify

Publish an MQTT OTA upgrade command to target devices, specifying the firmware version, download URL, and MD5 checksum to trigger remote updates.

Instructions

Publish MQTT OTA upgrade command (mcu_up) to target device topics.

Args: version: Firmware version string (e.g. '2.1.11'). file_url: Downloadable public URL of the uploaded firmware. md5: MD5 checksum of the firmware. board_id: Optional board identifier. device_ids: Target device ID(s) or topic(s). config_path: Optional custom firmware release config file.

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": {
      "version": "<version>",
      "file_url": "<file_url>",
      "md5": "<md5>"
    },
    "name": "firmware_notify"
  }
}

Input Schema

Name	Required	Description	Default
`md5`	Yes
`version`	Yes
`board_id`	No
`file_url`	Yes
`device_ids`	No
`config_path`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 9, 2026

TDQS

A3.7/5.0

Behavior2/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It reveals the mechanism (MQTT, mcu_up) but does not disclose side effects such as triggering a remote firmware update on target devices, whether devices must be online, or how success/failure is reported. For a remote-action tool this is a meaningful gap.

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 tightly written: one clear action sentence followed by a compact, well-labeled argument list. Every line adds value and no filler or restatement of the schema is present.

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

Completeness4/5

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

The description gives the core action and explains all six parameters, which is sufficient for correct invocation, especially since an output schema exists. It is slightly incomplete only in lacking workflow context and side-effect warnings, but those gaps are mostly captured in the usage and transparency dimensions.

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

Parameters5/5

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

With 0% schema description coverage, the Args section compensates fully: every parameter gets an explanatory line, including examples, optionality, URL purpose, checksum, and target semantics. This adds real meaning beyond the raw JSON schema types.

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 states a specific verb ('Publish') and resource ('MQTT OTA upgrade command') targeting device topics, and even names the command type ('mcu_up'). This clearly distinguishes it from sibling tools like firmware_upload, firmware_build, and firmware_release.

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 implies this is used to push OTA upgrade commands, but it gives no explicit guidance on when to choose this tool over alternatives, no prerequisites, and no mention of whether firmware_upload or firmware_build should precede it. An agent is left to infer the workflow.

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