Skip to main content
Glama
Sign In
Revel Digital MCP Server

Revel Digital MCP Server

Official
by RevelDigital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

getdevices

Retrieve all devices in your account with optional filters for organization, group, online status, and more.

Instructions

Gets all devices in an 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": "getdevices"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoUnique identifier for the device.
pageNoCurrent page number for paginated results.
takeNoMaximum number of items to retrieve in a query.
org_idNoUnique identifier for an organization to filter by.
group_idNoList of unique identifiers for media groups to filter by.
is_onlineNoFilter devices by their online status.
group_nameNoCollection of group names to filter by.
include_snapNoInclude the snapshot of the currently playing content. JPG format, base64 encoded.
device_type_idNoUnique identifier for the type of device.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.20

TDQS

B3/5.0
Behavior2/5

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

No annotations exist, and the description offers minimal behavioral context beyond 'gets devices.' It fails to disclose pagination, rate limits, or response characteristics, though the schema hints at pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (5 words) but lacks essential details; it is not optimally structured as it provides no additional context that aids invocation.

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 9 parameters, no annotations, no output schema, and many sibling tools, the description is inadequate. It omits pagination, filtering, and response structure, making it incomplete for effective use.

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 description coverage is 100%, so parameters are already documented. The tool description adds no extra meaning beyond the schema, meeting the baseline expectation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 the resource 'devices' with scope 'all in an account,' distinguishing it from sibling tools like getdevicebyid and postdevice.

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 usage guidelines are provided; the description does not indicate when to use this tool over alternatives, nor does it mention exclusions or prerequisites, leaving the agent without guidance.

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