Skip to main content
Glama

ai_modeling_remesh

Retopologize 3D models with triangle, quad, or Smart Mesh settings to control face count; use a stable request_id to safely reuse or avoid conflicting remesh jobs.

Instructions

retopologize a model with triangle, quad or Smart Mesh settings. Uses your Studio account and a stable request_id. Reuse returns the original job; changed input conflicts; outcome_unknown must never be blindly retried.

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": {
      "request_id": "<request_id>",
      "max_estimated_credits": "<max_estimated_credits>",
      "parameters": "<parameters>"
    },
    "name": "ai_modeling_remesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes
max_estimated_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already mark this as a non-read-only, non-destructive, open-world operation, and the description adds genuinely non-obvious behavior: it consumes the user's Studio account, it is idempotent via request_id, and conflicting reuse errors out. That idempotency and retry-safety disclosure is exactly the kind of context annotations cannot carry. It stops short of saying that credits are actually charged or what the returned job looks like.

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?

Three short sentences, front-loaded with the action and followed by the account/idempotency contract, with no filler. The telegraphic style ('changed input conflicts') is efficient but slightly compressed, and the credit/cost dimension is absent rather than trimmed.

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?

For a mutating, credit-consuming job submission with a nested parameter object, no output schema, and zero schema descriptions, the description covers the idempotency and account model well but omits the cost semantics of max_estimated_credits and the meaning of the geometry-defining fields. An agent could invoke it safely against the request_id contract but would be guessing about cost control and parameter effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full parameter burden and only partially does so: it explains the meaning of request_id as a stable idempotency key and hints that 'quad or Smart Mesh settings' correspond to mode flags. Nothing is said about max_estimated_credits (a required guard parameter), face_limit, bake, part_name_list, or expected_operator_id, leaving most of the nested object opaque.

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?

States a specific verb and resource ('retopologize a model') plus the three modes (triangle, quad, Smart Mesh), which maps onto the quad/smart_poly flags. It does not name a sibling it might be confused with, but within the ai_modeling_* family no clearly overlapping retopology tool is implied, so the purpose stands on its own.

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?

The description gives strong operational guidance about re-invocation (reuse request_id returns the original job, changed input conflicts, outcome_unknown must not be blindly retried), which is real when/how-to-call guidance. It does not, however, say when to pick this tool over anything else, nor state prerequisites such as needing a valid project_id or sufficient credit balance.

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