Skip to main content
Glama
mqtt-spec-mcp

mqtt-spec-mcp

by cartertinney

MQTT spec outline

mqtt_spec_outline
Read-onlyIdempotent

Browse section IDs and titles for MQTT 3.1.1 or 5.0 specifications, optionally under a parent section, to navigate the document outline and choose sections to retrieve.

Instructions

Section ids and titles of one MQTT version, for browsing.

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

Input Schema

NameRequiredDescriptionDefault
parentNoSection id.
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no restating. The description usefully adds that output is limited to ids and titles rather than section bodies, but says nothing about pagination, ordering, or the depth of the traversal.

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 with no filler, and the resource plus scope come first. It is arguably too terse for what the parent parameter implies, but no wording is wasted.

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?

With no output schema and only two params at half description coverage, the description leaves the traversal model undefined: an agent cannot tell from it whether passing 'parent' walks descendants or just lists immediate children, nor does it confirm the version parameter is required. For a browsing tool meant to be iterated over, that gap matters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% and the description adds little: 'one MQTT version' loosely signals the version parameter, but the enum values are already in the schema. The key ambiguity is untouched — whether 'parent' returns only direct children or a whole subtree, and what omitting it yields — which the schema's bare 'Section id' does not resolve.

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?

Names a concrete resource (section ids and titles) and scopes it to a single MQTT version, so an agent knows it retrieves an outline rather than section content. The verb is only implied by the fragment, and no sibling (mqtt_spec_get, mqtt_spec_lookup, mqtt_spec_search) is named or contrasted, so differentiation rests on the 'outline'/'browsing' wording alone.

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?

'For browsing' hints at exploratory use before drilling into a section, which is useful implied guidance. There is no explicit when-to-use, when-not-to-use, or statement of which sibling to pick for full content versus lookup versus search.

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