forge3d-mcp

Review Model

review_model

Validates, renders, and generates a preview card for a 3D model in one call, so you can confirm readiness before handoff and after each repair.

Instructions

One call for the whole review loop: validate + render + card.

Use this as the last step before telling a user the model is ready, and after every repair.

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": {
      "path": "<path>"
    },
    "name": "review_model"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`spec`	No
`previews`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.7Nov 4, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations, the description does the heavy lifting and usefully discloses that this call bundles three behaviors including rendering and card generation, which implies artifact writes. It does not say whether it is fail-fast or aggregates all issues, whether renders/cards are written to disk and where, or how expensive the call is.

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?

Two dense sentences, front-loaded with the composite scope before the timing guidance — no padding. The shorthand 'card' is slight jargon that could be clearer, but nothing is wasted.

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?

An output schema exists, so return values need no explanation. However, for a composite tool with zero annotation coverage and three undescribed parameters, the definition omits too much: what spec is for, what previews controls, and what side effects (files written) to expect.

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% for all three parameters. The description mentions 'render', which hints at the previews flag, but never explains path, spec, or what previews=true actually toggles. With three undocumented parameters, the description fails to compensate for the schema gap.

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 gives a specific composite action (review) decomposed into its three constituent operations: validate, render, card. An agent can tell it is a bundled review step rather than a single-purpose operation, though it never names the siblings (validate_model, render_model, model_card) that each sub-step corresponds to.

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 states explicit timing: use as the last step before declaring the model ready, and after every repair. That is clear, actionable context. It does not state when NOT to use it (e.g., for a quick validation-only pass, use validate_model instead), so the alternative routing is left implicit.

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