Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

snapshot_annotated

Capture an annotated JPEG using the detector's latest bounding boxes and return JSON detection metadata, frame timing, and an optional note for verifying camera detections.

Instructions

JPEG snapshot with the detector's latest boxes drawn, plus JSON {detections, det_frame_id, det_age_vs_frame_ms, note?}. Boxes come from the latest result and may lag the frame.

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_annotated"
  }
}

Input Schema

NameRequiredDescriptionDefault
qualityNo
max_widthNo
min_scoreNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the returned JSON fields and warns that boxes may lag the frame, which is a real behavioral caveat an agent must know. It stops short of saying whether the call is read-only, whether it triggers a fresh detection, or what the latency cost is.

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 dense sentences, front-loaded with the output format and followed by the staleness caveat. No filler; the field list is compact and each clause carries information.

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

Completeness3/5

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

The return payload is well covered, compensating for the absent output schema, and the lag caveat addresses a key risk. However, with three undocumented parameters and no annotations, the definition leaves the tuning knobs entirely opaque, which is a meaningful gap for a tool whose output quality depends on them.

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

Parameters2/5

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

All three parameters (quality, max_width, min_score) have 0% schema description coverage and are never mentioned in the description. The schema gives only types, defaults and ranges, so an agent gets no explanation of what min_score filters or how max_width downscaling affects the drawn boxes.

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?

States a specific verb+resource: a JPEG snapshot with the detector's latest boxes drawn, plus a named JSON payload. The 'annotated' qualifier and the box-overlay wording naturally separate it from the plain snapshot sibling and from detect, without needing to name them.

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?

Usage is only implied: an agent can infer this is for visual verification of detections, and the lag caveat hints at when it is unsuitable for precise timing. There is no explicit when-to-use versus snapshot or detect, and no stated exclusions.

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