Skip to main content
Glama
Sign In
MQTT MCP Server

MQTT MCP Server

by sergiudanstan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

mqtt_publish

Publish a message to an MQTT topic with adjustable quality of service and retain flag.

Instructions

Publish a message to an MQTT topic

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": {
      "topic": "<topic>",
      "message": "<message>"
    },
    "name": "mqtt_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe MQTT topic to publish to
messageYesThe message payload to publish
qosNoQuality of Service level (0, 1, or 2). Default is 0
retainNoWhether to retain the message on the broker. Default is false

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, and the description lacks details about side effects (e.g., requires an active connection, behavior of retain flag). It only states the basic action.

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 with no redundant information, efficiently conveying the tool's 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?

Given the lack of output schema and annotations, the description is adequate for a simple tool but omits important context like the need for a prior connection and the effect of the 'retain' parameter.

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

Parameters3/5

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

The input schema has 100% description coverage, so the description adds no new meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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 (publish) and resource (message to MQTT topic), making it easily distinguishable from sibling tools like mqtt_subscribe or mqtt_connect.

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 description implies when to use the tool (to send a message) but offers no explicit guidance on when not to use it or alternatives, which is a missed opportunity for clarity.

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