Skip to main content
Glama
Sign In
woow_emqx_mcp_server

woow_emqx_mcp_server

by WOOWTECH
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

EMQX Client Subscriptions

emqx_client_subscriptions
Read-onlyIdempotent

Check a client's subscribed topics and QoS to diagnose why a device isn't receiving messages.

Instructions

Which topics one client is subscribed to, with QoS.

Use this when a device "isn't receiving anything" — usually the subscription filter does not match the publish 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": {
      "clientid": "<clientid>"
    },
    "name": "emqx_client_subscriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientidYesExact client id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, idempotent behavior. The description adds useful diagnostic context (correlating with publish topic mismatches) and notes QoS is included, which goes beyond structured metadata without contradicting it.

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?

Two short sentences, front-loaded with the core purpose, followed by a practical usage tip. Every word earns its place with no redundancy.

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

Completeness5/5

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

With a simple one-parameter tool, full schema coverage, and an output schema present, the description sufficiently covers the what and when. The diagnostic context rounds out the tool's role without needing extensive elaboration.

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 schema fully describes the clientid parameter as 'Exact client id.' The description adds only that it refers to one client, which is already implied. No additional semantic detail is provided beyond the schema.

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 returns topics a single client is subscribed to, including QoS. This directly distinguishes it from sibling tools like emqx_list_subscriptions which likely covers all clients.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit use case: diagnosing a device not receiving messages, and hints at the likely cause (subscription filter mismatch). However, it does not explicitly mention alternatives or when not to use this tool.

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