Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

snapshot

Captures a JPEG frame from the camera stream with adjustable quality and width, returning image data plus JSON metadata (dimensions, device timestamp, age) for vision tasks.

Instructions

JPEG snapshot from the camera stream, plus JSON {width, height, device_ts_ms, age_ms}.

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": "snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
qualityNo
max_widthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses that the return includes JPEG image data plus JSON width, height, device timestamp, and age, but it says nothing about permissions, whether control of the camera is required, blocking behavior, or freshness guarantees.

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?

The definition is a single front-loaded sentence with no filler. Every clause contributes either the output format or the returned metadata fields.

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?

For a tool with two input parameters, no output schema, and no annotations, the description is too thin. It covers the return payload shape but leaves both input parameters unexplained and gives no operational context for when or how to invoke the snapshot.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented input parameters. It mentions output width and height but never explains the quality or max_width inputs, their ranges, or how they affect the returned JPEG.

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 states a specific verb and resource: a JPEG snapshot from the camera stream, and it names the accompanying JSON metadata fields. It does not differentiate from the sibling snapshot_annotated, so an agent cannot tell from this text alone which snapshot variant to choose.

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?

There is no explicit when-to-use guidance and no mention of alternatives. The presence of snapshot_annotated in the sibling set makes the omission more consequential, since the description gives no rule for choosing between plain and annotated snapshots.

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