Skip to main content
Glama
espressif

ESP RainMaker MCP Server

Official
by espressif

create_group

Create groups to organize ESP RainMaker devices into homes, rooms, or custom categories. Specify parent groups and add nodes as needed.

Instructions

Create a new group (home, room, or custom group) using Python library API.

Parameters:

  • name: Name of the group (required)

  • group_type: Type of group ('home', 'room', or custom type)

  • description: Description of the group (optional)

  • mutually_exclusive: Set mutually exclusive flag (recommended for homes and rooms)

  • parent_group_id: Parent group ID (required for rooms under a home)

  • nodes: Comma-separated list of node IDs to add to the group (optional)

  • custom_data: Custom data as JSON string (optional)

Examples:

  • Create home: create_group("My Home", "home", mutually_exclusive=True)

  • Create room: create_group("Living Room", "room", mutually_exclusive=True, parent_group_id="home_id")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
group_typeNo
descriptionNo
mutually_exclusiveNo
parent_group_idNo
nodesNo
custom_dataNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Despite no annotations, description adequately discloses the create operation, parameters, and usage examples. It does not detail response or side effects but is sufficiently transparent.

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?

Description is well-structured with purpose, parameter list, and examples. Slightly verbose due to examples, but front-loaded and effective.

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

Completeness5/5

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

For a creation tool with 7 parameters and an output schema, the description covers all parameters, provides usage guidance, and examples. No major gaps.

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

Parameters5/5

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

With 0% schema description coverage, the description compensates fully by listing all parameters with detailed explanations, examples, and recommendations (e.g., mutually_exclusive, parent_group_id for rooms).

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?

Description clearly states 'Create a new group (home, room, or custom group)', which is a specific verb and resource. It distinguishes from sibling tools like update_group and add_device_to_room.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description provides clear context for creating groups with types and examples, but does not explicitly state when not to use or alternatives like update_group.

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/espressif/esp-rainmaker-mcp'

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