Skip to main content
Glama
Sign In
MQTT MCP Server

MQTT MCP Server

by sergiudanstan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

mqtt_unsubscribe

Unsubscribe from a specified MQTT topic to stop receiving messages.

Instructions

Unsubscribe from 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>"
    },
    "name": "mqtt_unsubscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe MQTT topic to unsubscribe from

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?

With no annotations, the description fails to disclose behavioral traits. It does not indicate if the operation is safe, destructive, or requires establishing a connection first. Minimal information beyond the 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 that front-loads the core purpose. Every word is necessary, and no extraneous information is present.

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 low complexity, single parameter, and no output schema, the description is too brief. It omits important context such as connection requirements, error conditions, and relationship to the wider MQTT lifecycle (e.g., must be connected and subscribed 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 description coverage is 100% for the single parameter 'topic' with a clear description. The tool description adds no additional meaning beyond what the schema already provides, meeting but not exceeding the baseline.

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 'Unsubscribe from an MQTT topic' clearly states the action (unsubscribe) and resource (MQTT topic). It distinguishes from the sibling tool mqtt_subscribe by using the opposite verb.

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 (e.g., mqtt_subscribe or mqtt_disconnect). The description does not specify prerequisites like being connected or previously subscribed.

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