mcp2tcp
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 |
|---|---|
| pwmC | 把PWM调到最大 (frequency=100) |
| pico_infoB | 查询Pico板信息 |
| ledC | 打开LED (state=on) |
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: 'led' controls an LED, 'pico_info' queries board information, and 'pwm' adjusts PWM settings. There is no overlap in functionality, making it easy for an agent to select the correct tool for each task without confusion.
The naming is mixed in style: 'led' and 'pwm' are acronyms or abbreviations, while 'pico_info' uses snake_case. However, all names are short and readable, with no chaotic variations, but they lack a consistent verb_noun pattern or uniform casing.
With only 3 tools, the set feels thin for a server named 'mcp2tcp', which might imply broader capabilities like TCP communication or device control. While each tool is distinct, the count is borderline low for the apparent scope of interacting with a Pico board.
The tool surface is severely incomplete for controlling a Pico board via TCP. There are no tools for basic operations like reading sensor data, sending/receiving TCP data, or managing connections. The existing tools cover only LED, PWM, and info queries, leaving significant gaps that could cause agent failures in broader tasks.