Skip to main content
Glama

ai_modeling_brush_snapshot

Render a perspective Magic Brush input image and output its column-major Studio camera matrix for camera alignment and downstream 3D workflows.

Instructions

render a perspective Magic Brush input image and its column-major Studio camera matrix

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model_path": "<model_path>",
      "destination_path": "<destination_path>"
    },
    "name": "ai_modeling_brush_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
fovNo
sizeNo
azimuthNo
blenderNo
elevationNo
model_pathYes
destination_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.7/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, implying the call writes output somewhere, but the description never says the render is written to destination_path, whether existing files are overwritten, or what else is returned besides the matrix. With no output schema, the passing mention of a 'column-major Studio camera matrix' is the only return-value disclosure. For a mutating render tool this leaves meaningful behavioral gaps.

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?

A single front-loaded sentence with no filler or repetition. It is terse rather than bloated, so the weakness is under-specification rather than wordiness.

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?

Seven parameters with zero schema documentation, no output schema, and a write-type annotation the description never elaborates on make this too thin for the tool's complexity. An agent could not reliably construct arguments for fov, size, azimuth, or the two paths from this definition alone.

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?

Schema description coverage is 0% across 7 parameters, so the description is the only place parameter meaning could be conveyed, and it conveys essentially none. 'Perspective' loosely gestures at the camera controls (fov, azimuth, elevation), but there is no guidance on units, angle conventions, image size, the 'blender' string, or what model_path versus destination_path must point to.

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 names a specific verb ('render') and a concrete artifact ('perspective Magic Brush input image and its column-major Studio camera matrix'), so the agent knows exactly what the call produces. It does not differentiate itself from the similarly named siblings ai_modeling_snapshot or ai_modeling_brush_bake, which keeps it short of a 5.

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 statement of when this tool should be used versus ai_modeling_snapshot or the other brush tools, no prerequisites (e.g., whether a canvas/model must exist first), and no mention of when not to use it. The agent must infer the workflow position entirely from the name.

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

Deploy Server

Other Tools