add_resource_group_member
Add a monitor or service to a resource group by specifying member ID and type.
Instructions
Add a monitor to a resource group.
Required fields: monitorId.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| group_id | Yes | ||
| body | Yes |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Implementation Reference
- The add_resource_group_member tool handler. It accepts a group_id and an AddResourceGroupMemberRequest body, and calls the SDK's resource_groups.add_member() to add a monitor to a resource group. The body requires a 'memberType' and 'memberId' field (as per test_typed_schemas.py line 73).
@mcp.tool() def add_resource_group_member( group_id: str, body: AddResourceGroupMemberRequest, api_token: str | None = None, ) -> ToolResult: """Add a monitor to a resource group. Required fields: monitorId. """ try: return serialize( get_client(api_token).resource_groups.add_member( group_id, as_payload(body) ) ) except DevhelmError as e: raise_tool_error(e) - AddResourceGroupMemberRequest is imported from devhelm.types and used as the typed Pydantic model for the tool's body parameter. It defines the input schema for the member being added.
from devhelm.types import ( AddResourceGroupMemberRequest, CreateResourceGroupRequest, UpdateResourceGroupRequest, ) - src/devhelm_mcp/server.py:109-110 (registration)The tool is registered when server.py calls mod.register(mcp) for the resource_groups module (line 99 in the ALL_TOOL_MODULES list).
for mod in ALL_TOOL_MODULES: mod.register(mcp) - src/devhelm_mcp/tools/resource_groups.py:22-22 (registration)The register() function in resource_groups.py decorates add_resource_group_member with @mcp.tool() to register it as an MCP tool.
def register(mcp: FastMCP) -> None: