Skip to main content
Glama
mqtt-spec-mcp

mqtt-spec-mcp

by cartertinney

MQTT spec search

mqtt_spec_search
Read-onlyIdempotent

Searches MQTT 3.1.1 or 5.0 specification excerpts offline by question terms, helping agents find focused evidence to retrieve and cite.

Instructions

Evidence from one MQTT version: excerpts of the sections that best match the question.

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

Input Schema

NameRequiredDescriptionDefault
queryYesThe question's key terms; for several parts, one group per part, separated by ';'.
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 safety is covered. The description adds two useful facts beyond that: results are excerpts (not full sections) and they are ranked by best match, plus the per-call restriction to one version. It still omits how many excerpts come back and whether there is any scoring or ordering the agent can rely on.

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?

One short sentence with no filler; the key scope constraint (one MQTT version) is front-loaded. It is a sentence fragment rather than a complete statement of purpose, which slightly reduces the structural clarity.

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 two-parameter read-only tool with no output schema, the description covers the essentials, but it leaves open the differentiator against mqtt_spec_lookup and mqtt_spec_get and says nothing about result volume. Adequate as a minimum-viable definition, not fully complete.

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 50%: the 'query' parameter is documented (key terms, ';'-separated groups per part) while 'version' is only constrained by an enum ['3.1.1','5.0'] with no description. The description partially compensates by framing version as selecting which spec version the evidence comes from and query as the question being matched, but it adds no syntax or formatting detail beyond the schema.

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 makes clear this is a retrieval tool: it returns 'excerpts of the sections that best match the question' from 'one MQTT version.' The verb is implied rather than stated and no sibling (mqtt_spec_get, mqtt_spec_lookup, mqtt_spec_outline) is named, but an agent can tell it performs a matching search rather than a full-section fetch.

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?

There is no when-to-use or when-not-to-use guidance and no mention of the three sibling retrieval tools, so an agent must guess whether to search, look up, or get the outline. The only implied usage signal is that the call is scoped to a single MQTT version.

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