mcp2mqtt
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| set_pwmC | 设置PWM频率，范围0-100 |
| get_pico_infoC | 获取Pico开发板信息 |
| led_controlC | 控制LED开关 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_pico_info retrieves board information, led_control manages LED state, and set_pwm configures PWM frequency. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern (get_pico_info, led_control, set_pwm) with clear, descriptive actions. The naming is uniform and predictable across the set.
With 3 tools, the count is reasonable for controlling a Pico board, though it feels slightly minimal. The tools cover core operations (info, LED, PWM), but additional features like sensor reading might be expected in a broader scope.
The tools provide essential control functions for a Pico board (info, LED, PWM), covering basic hardware interactions. However, there are minor gaps, such as missing tools for reading sensors or configuring other peripherals, which agents might need for more complex tasks.