Skip to main content
Glama
devhelmhq

DevHelm MCP Server

Official
by devhelmhq

create_resource_group

Create a new resource group for organizing monitors with customizable alerting and health thresholds.

Instructions

Create a resource group.

Required fields: name. Optional: description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The create_resource_group tool handler function. Uses @mcp.tool() decorator. Takes a typed CreateResourceGroupRequest body (requires 'name', optional 'description'), calls the Devhelm SDK's resource_groups.create(), and serializes the result.
    @mcp.tool()
    def create_resource_group(
        body: CreateResourceGroupRequest,
        api_token: str | None = None,
    ) -> ToolResult:
        """Create a resource group.
    
        Required fields: name. Optional: description.
        """
        try:
            return serialize(
                get_client(api_token).resource_groups.create(as_payload(body))
            )
        except DevhelmError as e:
            raise_tool_error(e)
  • Imports the CreateResourceGroupRequest schema from devhelm.types, which defines the input validation (required field: name, optional: description).
    """Resource group tools — logical grouping of monitors."""
    
    from __future__ import annotations
    
    from devhelm import DevhelmError
    from devhelm.types import (
        AddResourceGroupMemberRequest,
        CreateResourceGroupRequest,
        UpdateResourceGroupRequest,
    )
    from fastmcp import FastMCP
  • The register() function is called by server.py (line 110: mod.register(mcp)) to register all resource group tools on the FastMCP instance. The @mcp.tool() decorator on line 39 registers 'create_resource_group'.
    def register(mcp: FastMCP) -> None:
        @mcp.tool()
  • The server iterates ALL_TOOL_MODULES (which includes resource_groups) and calls mod.register(mcp) to register all tools, including create_resource_group.
    ALL_TOOL_MODULES = [
        monitors,
        incidents,
        forensics,
        alert_channels,
        notification_policies,
        environments,
        secrets,
        tags,
        resource_groups,
        webhooks,
        api_keys,
        dependencies,
        deploy_lock,
        maintenance_windows,
        status,
        status_pages,
    ]
    
    for mod in ALL_TOOL_MODULES:
        mod.register(mcp)
  • Imports helper utilities used by create_resource_group: ToolResult, as_payload (converts Pydantic model to dict), get_client (builds SDK client), raise_tool_error (converts SDK errors to MCP ToolError), and serialize (formats results).
    from devhelm_mcp.client import (
        ToolResult,
        as_payload,
        get_client,
        raise_tool_error,
        serialize,
    )
Behavior2/5

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

No annotations; description only states 'Create' and lists required fields. No disclosure of idempotency, permissions, duplicates, 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?

Two concise sentences, front-loaded. However, brevity sacrifices useful context; could include more with same structure.

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

Completeness2/5

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

Tool has complex input schema with many optional nested fields; description fails to explain purpose of resource groups, relation to other tools, or any behavioral details.

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?

Description redundantly states 'Required fields: name. Optional: description.' Schema already documents all fields with descriptions. Minimal added value beyond schema.

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?

Clearly states 'Create a resource group' with verb and resource. But lacks differentiation from many other 'create_*' sibling tools, missing context on what a resource group is.

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 vs alternatives like create_monitor. No prerequisites, exclusions, or context provided.

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/devhelmhq/mcp-server'

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