Skip to main content
Glama
Sign In
MQTT MCP Server

MQTT MCP Server

by sergiudanstan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

mqtt_subscribe

Subscribe to an MQTT topic and receive incoming messages. Supports wildcards for single and multi-level topics.

Instructions

Subscribe to an MQTT topic to receive messages

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>"
    },
    "name": "mqtt_subscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe MQTT topic to subscribe to (supports wildcards: + for single level, # for multi-level)
qosNoQuality of Service level (0, 1, or 2). Default is 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so the description must disclose behavior. It only states the basic action but fails to mention persistence of subscription, event handling, or the need for prior connection.

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. Front-loaded with verb and resource.

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?

Given no output schema and no annotations, the description is too minimal. It does not explain what the agent can expect after subscribing (e.g., message reception) or that a connection must be established first.

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?

Schema coverage is 100% with descriptions for both parameters. The description does not add additional meaning beyond the schema, so baseline 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 (Subscribe) and the resource (MQTT topic) and the purpose (to receive messages). It effectively distinguishes from sibling tools like mqtt_publish, mqtt_connect, etc.

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 on when to use this tool versus alternatives. It does not mention prerequisites like requiring an active connection via mqtt_connect, nor does it indicate when not to use it.

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