Skip to main content
Glama
Ref2Blender MCP Server

Ref2Blender MCP Server

by evarynstudio

check_model

Generates a game-readiness report covering triangle budget, materials, missing UVs, n-gons, and warnings to fix before finishing a 3D model.

Instructions

Game-readiness report: triangles (against the budget, if given), materials, missing UVs, n-gons, and warnings to fix before the model is finished.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNo
triangle_budgetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It implies a read-only inspection through 'report' and 'check', but never states that the tool is non-destructive, whether it requires an active/selected mesh object, or what it does when no asset is specified. The list of inspected categories is useful, yet the operational preconditions that matter most for a scene-inspection tool are absent.

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 whose parenthetical and list are ordered by importance, with the actionable framing ('warnings to fix') last. Dense but not padded; every clause names a distinct check.

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?

The output schema covers return values, so the description need not describe the report format. What is left unaddressed — the meaning of the 'asset' parameter and any preconditions on the scene state — is significant for a two-parameter validation tool, so the definition is adequate but not complete.

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 coverage is 0% across two parameters. The description does explain triangle_budget via 'against the budget, if given', including the idea that the comparison is optional. The 'asset' parameter, however, is never mentioned — the agent cannot tell whether it expects an object name, ID, file path, or whether null means the active selection.

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 operation (a game-readiness report) on a specific resource (the model) and enumerates the checks: triangles, materials, missing UVs, n-gons, warnings. That is far more informative than a restatement of 'check_model' and distinguishes it from siblings such as scene_summary or render_views. It stops short of 5 only because it never explicitly contrasts itself with those siblings.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'warnings to fix before the model is finished', which tells the agent this is a pre-completion validation step. There is no explicit statement of when to prefer this over scene_summary or blender_status, and no exclusion or prerequisite conditions are given.

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