Skip to main content
Glama
mqtt-spec-mcp

mqtt-spec-mcp

by cartertinney

MQTT spec get section

mqtt_spec_get
Read-onlyIdempotent

Retrieve a specific section of the MQTT 3.1.1 or 5.0 specification as Markdown, and continue paged content using the Next cursor.

Instructions

One section of one MQTT version as Markdown pages; continue a page with its Next cursor.

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

Input Schema

NameRequiredDescriptionDefault
cursorNoNext cursor.
sectionYesSection id or title.
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description only has to add context beyond that. It does so by disclosing the Markdown page format and multi-page paging with a Next cursor, which the schema and annotations don't state. It still doesn't say how large a page is or how the consumer knows it has reached the end of the section.

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?

It is a single dense sentence with no filler and leads with the resource and the return format. The paging advice is appended as a clause, so it is slightly buried and is not front-loaded.

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

Completeness4/5

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

Because this is a trivial read-only tool with annotations covering its safety profile and a three-parameter schema, very little prose is needed. What remains missing is paging completion behavior and how the section is identified, but an agent can still call it correctly.

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 67% schema description coverage, the schema already documents cursor and the version enum, while the section parameter is labeled 'Section id or title.' The description adds a bit of meaning by explaining that the cursor continues a page, but gives no detail on how section ids or titles are formed.

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 a concrete resource (a section of a specific MQTT version) and the return format (Markdown pages). The retrieval verb is implicit rather than stated, and it never distinguishes this tool from the sibling lookup/search/outline tools.

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?

It tells you how to continue a multi-page section using the Next cursor, which is real when-to-use guidance for pagination. It gives no guidance on when to pick this over mqtt_spec_lookup, mqtt_spec_outline, or mqtt_spec_search.

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