Skip to main content
Glama
Sign In
MCP API Bridge Server

MCP API Bridge Server

by marty5499
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mqtt_register_handler

Register a handler for MQTT messages by specifying device ID, action, and JavaScript handler code to process incoming messages.

Instructions

註冊 MQTT 訊息處理器

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": {
      "deviceId": "<deviceId>",
      "action": "<action>",
      "handlerCode": "<handlerCode>"
    },
    "name": "mqtt_register_handler"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes要處理的動作名稱
deviceIdYes裝置 ID
handlerCodeYes處理器函數程式碼 (JavaScript)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

C2.7/5.0
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the tool registers a handler, but omits critical behaviors: whether it overwrites existing handlers, if the JavaScript code is executed server-side, security implications, or persistence. This lack of transparency leaves the agent uninformed.

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?

The description is a single short sentence in Chinese, which is concise but not overly terse. It is front-loaded with the main verb and object. However, a slightly more informative description could improve without sacrificing conciseness.

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?

Given the complexity of registering a handler with executable code, the description is insufficient. It does not explain the handler's lifecycle, trigger mechanisms, return values, or error conditions. The schema covers parameter details but the description lacks essential operational context.

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 input schema already provides descriptions for all three parameters (100% coverage), so the baseline is 3. The tool description adds no additional parameter context beyond what the schema offers. Thus, it meets the baseline but does not exceed it.

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 '註冊 MQTT 訊息處理器' (Register MQTT message handler) clearly states the action and resource. However, it does not differentiate from sibling tools like mqtt_subscribe, which might be confused with handler registration. The input schema further clarifies the purpose by specifying deviceId, action, and handlerCode.

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?

The description provides no guidance on when to use this tool versus alternatives. No prerequisites, exclusions, or context for choosing this over mqtt_subscribe or mqtt_publish. The agent must infer usage solely from the tool name and schema.

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