Skip to main content
Glama
Sign In
Revel Digital MCP Server

Revel Digital MCP Server

Official
by RevelDigital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

getdevicegroups

Retrieves device groups from your Revel Digital account. Use it to list or view details of device groups, with options for pagination and hierarchical data.

Instructions

Gets device groups in the account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getdevicegroups"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOptional group id
pageNoOptional number of page to return
takeNoOptional number of items to return
treeNoOptional hierarchical data format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.20

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states 'Gets device groups'. It fails to disclose that the tool supports pagination (page/take), filtering by id, or hierarchical output via tree. No mention of idempotency, authentication, 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?

The description is a single, concise sentence with no unnecessary words. It could benefit from slightly more context without becoming verbose.

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?

Given 4 optional parameters and no output schema, the description is incomplete. It omits the existence of filtering, pagination, and hierarchical data formatting, which are crucial for an agent to invoke correctly.

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?

Schema coverage is 100%, so each parameter has a description. The tool description adds no extra meaning beyond the schema, meeting the baseline but not compensating for any gaps.

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?

The description clearly states the verb 'gets' and resource 'device groups', distinguishing it from siblings like 'getdevices' or 'getdevicebyid'. However, it doesn't specify whether it retrieves all groups or a single group by ID, relying on the optional 'id' parameter.

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 is provided on when to use this tool versus alternatives such as 'getdevices' for device-level operations or group mutation tools. There is no mention of prerequisites or typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools