probe_framing

shallow

info.3dcms/mcp · Verify this server

Read a saved camera (cameraId), or an exact pose, as a visitor sees it at the screen shapes they actually have (16:9 desktop and 9:16 phone by default), against the rules a photographer and a web designer use. Analytic and instant: the published viewer's own camera pose, no render. A PAGE shot (a page's own camera, its arrivalCameraId or a camera inside the page, with the card in view) should hold the whole card on every screen, most of the width, within 60 degrees of square so its text still reads: centred is right for a page. A SCENE shot (a room, an object, a place, and the entry view even with a page in it: a 3D view need not be head-on) puts its subject on a third, the horizon on a third, the eye at a standing person's 1.5 to 1.7 m. The subject is the declared primary action (settings.design, or the page's data.primaryActionId), else the page's h1, else the biggest thing in frame. Returns, per screen shape: where the subject lands (x and y from -1 to 1, its thirds cell, how far from a power point, its share of the frame, whether all of it is in frame or which edge cuts it, whether text is legible), the page card (whole, width share, degrees off square), text the frame cuts, a near object cut in the foreground, the horizon row, the eye height above the floor (a phone backs a fitWidth camera up along its tilt, so read it on every shape), anything in the lens or around it, how much is in frame, and exits (signs and tap targets within 12 m, in frame or not). Then `findings` in plain sentences, worst first, and `suggest`: one pose that fixes the composition, judged as the viewer builds it on every shape, with the sentence saying why, and `suggest.op`, a ready apply_ops update for this camera (null when the camera already stands at the best pose the probe can find). Call it on every entry and arrival camera you place, before get_scene_screenshot. On a scene you are building, apply the suggestion yourself when it serves the brief; on the user's own existing work, tell them what it found and offer the fix.

100.0/100

1 trials · measured 14 days ago

probe_framing scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against info.3dcms/mcp, measured 23 Sept 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
gated
Category
Content & media
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-09-23100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: probe_framing
[![Vouch score](https://vouch.tools/api/tools/f1d13491-bbe7-444b-b943-254f4568eff7/badge.svg)](https://vouch.tools/tools/f1d13491-bbe7-444b-b943-254f4568eff7)
probe_framing — Vouch