Create a resource group with a required name and optional policies to organize uptime monitors and manage alerting, health thresholds, and incident behavior.
Create a resource group.
Required fields: name. Optional: description.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.7.0Input schema / properties / body / properties / defaultRetryStrategy / anyOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "interval": {
- "description": "Delay between retry attempts in seconds",
- "type": "integer"
- },
- "maxRetries": {
- "description": "Maximum number of retries after a failed check",
- "type": "integer"
- },
- "type": {
- "description": "Retry strategy kind, e.g. fixed interval between attempts",
- "type": "string"
- }
- },
- "required": [
- "type",
- "maxRetries",
- "interval"
- ],
- "type": "object"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "properties": {
+ "interval": {
+ "description": "Delay between retry attempts in seconds",
+ "type": "integer"
+ },
+ "maxRetries": {
+ "description": "Maximum number of retries after a failed check",
+ "type": "integer"
+ },
+ "type": {
+ "description": "Retry strategy kind, e.g. fixed interval between attempts",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "maxRetries",
+ "interval"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / body / properties / description / anyOfPrevious value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "maxLength": 500,
+ "minLength": 0,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / body / properties / description / descriptionPrevious value: -"Optional description"New value: +"Optional description (max 500)"v1.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It states that the tool creates a resource group but does not disclose side effects, uniqueness constraints, whether creation is idempotent, permission requirements, or how defaults are applied to the group.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short, front-loaded with the action, and avoids filler. The required/optional field summary is placed after the action in a readable way, though the brevity does leave out important parameter context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool accepts a complex nested body with many optional settings, but the description only covers name and description. It does not explain how the other options affect the created group, what defaults apply, or what practical considerations exist, leaving an agent under-informed for a rich creation operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description says 'Required fields: name. Optional: description', which is a useful summary, but the schema contains many other optional fields like managedBy, alertPolicyId, defaultRegions, and defaultFrequency that are omitted. With 0% schema description coverage at the top level, the description fails to adequately compensate for the full parameter surface.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with 'Create a resource group', which is a clear verb + resource statement that tells an agent the core intent. It does not explicitly contrast with sibling tools like update_resource_group or delete_resource_group, but the create action itself is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives. The description mentions required and optional fields but does not state prerequisites, when a new group should be created, or when to use sibling tools such as update_resource_group or add_resource_group_member.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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