Skip to main content
Glama
espressif

ESP RainMaker MCP Server

Official
by espressif

get_group_details

Retrieve group information and node details for ESP RainMaker devices. List all groups or show a specific group with customizable fields.

Instructions

Get comprehensive group information using Python library API.

Parameters:

  • group_id: ID of specific group to show (optional - if None, lists all groups)

  • include_nodes: Include detailed node information for groups

  • fields: List of group/sub-group keys to include (if None, includes all fields)

  • node_fields: List of node keys to include (if None, includes all node fields)

When group_id is None: Lists all groups with hierarchy When group_id is provided: Shows detailed information for that specific group When include_nodes is True: Includes comprehensive node details within groups


IMPORTANT USAGE GUIDELINES:

  1. For home/room structure overview (recommended for most queries):

    {
        "include_nodes": true,
        "fields": ["group_id", "group_name", "type", "total", "sub_groups", "node_details"],
        "node_fields": ["node_id", "name", "type"]
    }
  2. For home/room structure with basic device info:

    {
        "include_nodes": true,
        "fields": ["group_id", "group_name", "type", "total", "sub_groups", "node_details"],
        "node_fields": ["node_id", "name", "type", "model", "fw_version"]
    }
  3. For detailed technical information:

    {
        "include_nodes": true,
        "fields": ["group_id", "group_name", "type", "total", "sub_groups", "node_details",
                  "is_matter", "fabric_id", "primary", "mutually_exclusive"],
        "node_fields": ["node_id", "name", "type", "model", "fw_version", "status", "params"]
    }

Common Use Cases:

Query Type

Recommended Fields

"Show my home"

Basic fields (option 1) to avoid large responses

"List my devices"

Basic fields (option 1) for clear device listing

"Check my rooms"

Basic fields (option 1) for room structure

"Device details"

Detailed fields (option 3) for full information

Note: When fields/node_fields are not provided, defaults to summary mode (basic fields) to avoid overwhelming responses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idNo
include_nodesNo
fieldsNo
node_fieldsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It explains behavior for different group_id values, include_nodes flag, and default field behavior. Lacks explicit mention of read-only nature or side effects.

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?

Well-structured with sections, but somewhat lengthy. Front-loaded with purpose, uses markdown and tables for clarity. A few sentences could be trimmed without losing value.

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?

Given 4 optional parameters and no annotations, the description covers all scenarios: summary mode vs. detailed, use cases, and example JSON. With an output schema defined, return value explanation is unnecessary.

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?

Schema has 0% description coverage, but the description fully explains all four parameters: their purpose, optionality, and effect on output. Adds meaning far beyond the bare schema.

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 starts with 'Get comprehensive group information', clearly defining the action and resource. It distinguishes from sibling tools like get_node_details and get_nodes by focusing on groups.

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?

Provides extensive usage guidelines with recommended parameter combinations and a query-type table. However, it does not explicitly state when to use alternatives or when not to use this tool.

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