Skip to main content
Glama
rhinocap

Raven MCP

by rhinocap
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Hybrid

audit_device_frame

Read-onlyIdempotent

Detect cropped content in device-mockup frames: flag object-fit cover crop loss, Ken Burns pan/zoom drift, and content truncated at edges. Ensures full media is visible in previews.

Instructions

Detect cropped content in device-mockup frames (phone/MacBook screenshots, app-preview clips). Three checks: (1) GEOMETRY — call with frames (container box + intrinsic media size + object-fit/position; call with NO args for a DevTools snippet) to flag object-fit:cover crop loss when the frame's aspect ratio ≠ the media's; (2) MOTION — pass clips (first/last frame PNG paths) to detect baked-in pan/zoom (Ken Burns) that drifts the composition; (3) EDGE — pass edge_frames (PNG paths) to flag content truncated at a frame edge. Catches the exact failure where a 16:9 clip in a 1.82-AR screen cutout silently slices the bottom, or a Ken-Burns-zoomed source crops content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clipsNoPer-clip first/last frame PNG file paths — detects baked-in pan/zoom (Ken Burns).
framesNoDevice-frame geometry samples (from the DevTools snippet): container box + intrinsic media size + computed object-fit/position. Flags object-fit:cover crop loss.
edge_framesNoFrame PNG file paths to check for content truncated at a frame edge (reuses edge-symmetry).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.9

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds value beyond annotations by revealing the no-args DevTools-snippet behavior and by explaining what each invocation actually analyzes.

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 well structured with numbered check categories and a front-loaded purpose statement. It is a little long, but the length is justified by having three distinct modes with different inputs.

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?

With zero required parameters and three optional modes, the description thoroughly explains when and how to call the tool. The only real gap is that there is no output schema and the description does not state the expected result format beyond saying content is 'flagged'.

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

Parameters4/5

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

The schema covers all parameters well, but the description adds operational meaning: `frames` is for aspect-ratio/crop geometry, `clips` for baked-in pan/zoom, and `edge_frames` for truncated content. This directly helps an agent decide which optional argument to supply.

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 opens with a clear verb and resource: 'Detect cropped content in device-mockup frames' and then enumerates three precise checks (GEOMETRY, MOTION, EDGE). This makes it easy to distinguish from generic page/video audit siblings.

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

Usage Guidelines4/5

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

It gives explicit usage modes: pass `frames` for geometry, `clips` for motion/Ken Burns, `edge_frames` for truncation, and no args to get a DevTools snippet. It does not explicitly state when to prefer an alternative tool for non-device-frame audit cases.

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

Install Server

Other Tools