Skip to main content
Glama

pico_info

Retrieve information about Pico boards connected through the mcp2tcp server, enabling AI models to access hardware data via TCP communication.

Instructions

查询Pico板信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the 'pico_info' tool logic, providing device information including uptime, PWM frequency, LED state in JSON format.
    def get_pico_info(self):
        uptime = int(time.time() - self.start_time)
        info = {
            "device": "Raspberry Pi Pico",
            "firmware_version": "1.0.0",
            "current_pwm": self.pwm_frequency,
            "led_state": self.led_state,
            "uptime_seconds": uptime
        }
        return f"CMD {json.dumps(info)}\r\n"
  • Registration and dispatching logic for the 'CMD_PICO_INFO' command, which corresponds to the 'pico_info' tool, routing to the handler.
    # 处理Pico信息查询命令
    elif command == "CMD_PICO_INFO":
        return device_state.get_pico_info()
Behavior2/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. '查询' (query) implies a read-only operation, but the description doesn't explicitly state this or mention any other behavioral traits like authentication requirements, rate limits, error conditions, or what format the information returns. For a tool with zero annotation coverage, this is inadequate behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at just four Chinese characters ('查询Pico板信息'), which directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple query tool with no parameters, and the meaning is immediately clear without unnecessary elaboration.

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

Completeness3/5

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

For a zero-parameter query tool with no annotations and no output schema, the description provides the minimum viable information about what the tool does. However, it doesn't explain what information is returned or in what format, which would be helpful given the lack of output schema. The description is complete enough to understand the basic purpose but lacks details about the tool's behavior and output.

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

Parameters4/5

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

The tool has zero parameters with 100% schema description coverage, so the baseline is 4. The description doesn't need to explain parameters since none exist, and it correctly doesn't attempt to describe non-existent parameters. The description focuses appropriately on the tool's purpose rather than parameter details.

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 '查询Pico板信息' clearly states the tool's purpose as querying information about a Pico board, using a specific verb ('查询' - query) and resource ('Pico板' - Pico board). It distinguishes from sibling tools 'led' and 'pwm' which likely control hardware components rather than query information. However, it doesn't specify what type of information is retrieved, keeping it from a perfect score.

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. It doesn't mention when this tool is appropriate, what prerequisites might exist, or how it differs from the 'led' and 'pwm' sibling tools. The agent receives no usage context beyond the basic purpose statement.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mcp2everything/mcp2tcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server