deletedevicegroup
Delete an empty device group by providing its ID to remove it from your digital signage system.
Instructions
Group must be empty.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Device group Id |
Delete an empty device group by providing its ID to remove it from your digital signage system.
Group must be empty.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Device group Id |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses only that the group must be empty, but lacks details on destructive nature, error behavior, or permissions. The precondition is useful but insufficient.
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?
Extremely concise but at the expense of clarity. Three words provide only a precondition, not the tool's purpose. Effective conciseness would include the action.
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?
With no output schema and only one parameter, the description is critically incomplete. It fails to state the tool's function, prerequisites beyond emptiness, or any side effects, making it unusable for an AI agent.
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?
Schema coverage is 100% with one parameter described as 'Device group Id'. The description adds no extra meaning beyond this; it does not explain the parameter's role in context of the tool.
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 does not state what the tool does; it only says 'Group must be empty.' The name 'deletedevicegroup' implies deletion, but the description fails to confirm this action, making it misleading for agents.
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 on when to use this tool versus siblings like deletemediagroup or deleteplaylistgroup. The precondition is mentioned but no context on prerequisites or alternatives.
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/RevelDigital/reveldigital-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server