Skip to main content
Glama

ai_modeling_model_rig

Binds a supported skeleton preset to an existing 3D model for rigging, using a stable request_id to return the original job on reuse and prevent blind retries after unknown outcomes.

Instructions

bind a supported skeleton to a model. 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_model_rig"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes
max_estimated_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only say readOnly=false, destructive=false, openWorld=true. The description adds real behavioral context beyond that: it consumes Studio account credits, request_id makes it idempotent (reuse returns the original job, changed input conflicts), and outcome_unknown is a non-retryable state. It stops short of describing what force=true does or what a conflicting-input rejection looks like, which would have made it a 5.

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?

Four short clauses with the purpose front-loaded and no filler; the idempotency facts are delivered telegraphically. Slightly clip-like phrasing ("Uses your Studio account") costs a little readability 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?

Given a mutation tool with nested parameters, no output schema, and no annotation coverage of side effects, the description covers the riskiest failure mode (idempotency/retry) but not the response shape or the credit-capping contract. An agent still cannot predict what comes back after a successful bind or how many credits it will spend.

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%, so the description must carry the parameter burden, and it only partly does. It explains request_id as a stable idempotency key, but gives no meaning for the required max_estimated_credits cap or for any of the nested parameters (project_id, rig_type, skeleton_preset, model_version, force, expected_operator_id).

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: "bind a supported skeleton to a model", which unambiguously identifies a rigging operation rather than generation, animation, or export. It does not name or differentiate itself from the closest sibling, ai_modeling_rig_check, leaving the agent to infer the relationship.

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 idempotency and retry guidance (reuse request_id, never blindly retry outcome_unknown) is genuinely actionable usage advice for this call. However, it says nothing about when to prefer this tool over ai_modeling_rig_check or when rigging is appropriate relative to model_generate, and no prerequisites or preconditions for a "supported skeleton" are given.

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