MyClaw Toolkit MCP Server

wifi_qrcode

Generate a QR code for WiFi networks by providing SSID, password, and security type, enabling instant connection on scanning.

Instructions

Generate WiFi connection QR codes

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": {
      "ssid": "<ssid>",
      "password": "<password>"
    },
    "name": "wifi_qrcode"
  }
}

Input Schema

Name	Required	Description	Default
`ssid`	Yes	WiFi network name (SSID)
`password`	Yes	WiFi password
`security`	No	Security type	WPA

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Jun 23, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, yet the description does not disclose behavioral traits like output format (e.g., image URL, base64), side effects, or any limitations. The user is left unaware of what to expect.

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, concise sentence that directly conveys the tool's purpose. It is front-loaded and efficient, though adding a brief note on output would improve it.

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?

Given the tool's simplicity (3 parameters, no nested objects, no output schema), the description is adequate but does not fully explain the output or any constraints (e.g., required fields). It meets minimum viability.

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 complete descriptions for all parameters (100% coverage). The description adds no additional meaning beyond what the schema states, meeting the baseline for this dimension.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: generating WiFi connection QR codes. It uses a specific verb and resource, and distinguishes itself from sibling tools like 'qrcode' by specifying WiFi.

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?

No guidance on when to use this tool versus alternatives such as 'qrcode' or other QR code generators. The description does not mention prerequisites or context.

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