Skip to main content
Glama
mqtt-spec-mcp

mqtt-spec-mcp

by cartertinney

MQTT spec lookup

mqtt_spec_lookup
Read-onlyIdempotent

Look up an exact MQTT 3.1.1 or 5.0 specification entry by packet, property, reason code, return code, requirement label, or glossary term to retrieve the precise definition and citation.

Instructions

Exact entry for one packet, property or reason_code (5.0), return_code (3.1.1), requirement label or glossary term.

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>",
      "kind": "<kind>",
      "query": "<query>"
    },
    "name": "mqtt_spec_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
queryYesExact name, number or label.
packetNoPacket filter.
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only that a single exact entry is returned — it does not say what happens when nothing matches, whether kinds are restricted per version, or what the returned entry contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence fragment with zero filler; the core noun phrase (exact entry) leads. It is arguably over-compressed — lacking a verb and any closing context — but nothing is wasted.

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?

For a 4-parameter, 3-required lookup with no output schema, the definition covers the lookup target but omits the packet filter's role, behavior on a failed exact match, and any sense of what the entry contains. Adequate but with visible gaps an agent would hit on first invocation.

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?

At 50% schema coverage the description does add real value by coupling kinds to versions (reason_code is 5.0-only, return_code is 3.1.1-only), which the enum alone does not express. However the optional `packet` filter remains unexplained in both schema ("Packet filter") and description, so the gap is only partly filled.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource types it resolves (packet, property, reason_code, return_code, requirement label, glossary term), which maps directly to the `kind` enum, and the word "Exact" signals a precise single-entry lookup rather than a search. It is clear what the tool does, though it never names or contrasts the actual siblings (mqtt_spec_search, mqtt_spec_outline, mqtt_spec_get).

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?

Guidance is only implied: "Exact entry" suggests using this for known exact names/numbers versus a search tool for exploratory queries, but there is no explicit when-to-use, when-not, or alternative named. An agent can infer the intent but must guess at the boundary against mqtt_spec_search and mqtt_spec_get.

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