Skip to main content
Glama

match_camera

Align a Blender camera to a reference photo by tuning position, rotation, roll, and field of view until the 3D model silhouette matches the target outline.

Instructions

Find the camera that shows the model like a perspective photo of the real object (for flat orthographic views use compare_view). It tunes position, rotation, roll and field of view until the model silhouette best matches the reference silhouette. The camera camera is created or updated and becomes the scene camera. The answer has location, rotation, look_at, fov_deg and the IoU before and after. Give the whole original photo, not a crop: the picture frame is the camera frame. The outline comes from alpha or from the corner colour (plain background); threshold is the colour distance. Start: init {"location": [x,y,z], "look_at": [x,y,z], "fov_deg": 40}, else the active perspective camera, else 8 azimuths at 2 elevations are tried. A close start gives a better result. fov_deg fixes the angle across the LONGER image side: a known lens is far more reliable, because distance and field of view trade off. ground_z keeps the camera above that height. size is the working resolution; iterations is how many times the step is halved. A silhouette does not tell front from back on a symmetric model: check with overlay_reference. Background job: after wait seconds the answer is a job id for job_status.

Input Schema

NameRequiredDescriptionDefault
initNo
sizeNo
waitNo
namesNo
cameraNomatch_cam
fov_degNo
ground_zNo
referenceYes
thresholdNo
iterationsNo
time_limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that the camera is created/updated and becomes the scene camera (a side effect), the fallback starting strategies, the background-job mode returning a job id for job_status after `wait` seconds, and the exact return fields (location, rotation, look_at, fov_deg, IoU before/after). This is rich behavioral context consistent with readOnlyHint=false.

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?

Dense and front-loaded, with the core purpose and alternative stated first. Most sentences earn their place, though the parameter-detail block is long and could be tightened slightly.

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 an 11-param mutation tool with no output schema, it covers the essential behavior, starting conditions, return values, and background-job path. The gaps are minor (undocumented `names` and `time_limit`).

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?

With 0% schema coverage across 11 parameters, the description compensates well: it explains init with an example, fov_deg semantics (angle fixed on the longer image side, distance/FOV tradeoff), ground_z, size, iterations, threshold, camera, reference, and wait. Only `names` and `time_limit` are left undocumented.

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 ('Find the camera that shows the model like a perspective photo') and immediately distinguishes itself from the sibling compare_view for flat orthographic views. An agent can identify the tool and its scope without opening the schema.

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?

Names the alternative compare_view and the condition selecting it, and points to overlay_reference for the front/back ambiguity on symmetric models. It also gives start-condition guidance, but does not state explicit when-not-to-use boundaries beyond the orthographic case.

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