Skip to main content
Glama
Sign In
Revel Digital MCP Server

Revel Digital MCP Server

Official
by RevelDigital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

getsnapshot

Capture a real-time JPEG screenshot from a digital signage device to verify on-screen content.

Instructions

Gets current snapshot of the device screen. Image is returned as a JPEG image.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "registrationKey": "<registrationKey>"
    },
    "name": "getsnapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
base64NoIf true, the JPG image will be returned as a base64-encoded string
registrationKeyYesDevice registration key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.20

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It states the snapshot is current and the image is JPEG. However, it does not mention required permissions, potential destructive actions, rate limits, or whether the snapshot is from the device's actual screen. Basic but not comprehensive.

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

Conciseness5/5

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

Two sentences, no redundant words. The key points (action, resource, output format) are front-loaded. Every sentence serves a purpose.

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

Completeness4/5

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

For a simple screenshot tool with no output schema, the description covers purpose and output format. It hints at the response via the base64 parameter. Could add details like typical file size or performance but is sufficient for selection and invocation.

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%, and the description adds minimal extra meaning. The base64 parameter's effect is already described in the schema. No additional semantic detail beyond the schema fields.

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 explicitly states the action 'gets snapshot' and the resource 'device screen', and clarifies the output format as JPEG. It is unambiguous and distinct from sibling tools which deal with accounts, devices, media, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for capturing a device screen snapshot but provides no guidance on when to use versus alternatives like getmedia or getdevicebyid. No exclusions, prerequisites, or context for when not to use.

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