Skip to main content
Glama

ai_modeling_resegment

Resegment the current 3D model by granularity level or custom prompt, using your Studio account and a stable request ID so repeated calls return the original job.

Instructions

resegment the current model using a level or custom prompt. 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_resegment"
  }
}

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 only mark this as non-read-only, open-world, non-destructive; the description goes well beyond that by disclosing the idempotency contract — same request_id returns the original job, changed input conflicts, and outcome_unknown must not be retried. It stops short of saying what credits are consumed or what happens to the existing model's prior segmentation.

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, then the idempotency rules. Slightly telegraphic — 'outcome_unknown' is used as if self-explanatory and no guidance is given on where that state is observed — but there is no filler.

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 credit-consuming job-creating tool with a nested parameter object and no output schema, the definition covers the idempotency semantics but omits the credit cap meaning, the expected_operator_id conflict behavior, and the returned job shape. An agent could call it, but would be guessing on cost and on the concurrency guard.

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 must compensate, and it partially does: it explains the request_id stability contract and hints that 'level' maps to a granularity choice versus a free-text prompt. It says nothing about max_estimated_credits, project_id, operator_id, expected_operator_id (optimistic concurrency?), or model_version, leaving most nested fields uninterpreted.

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 opens with a specific verb+resource ('resegment the current model') and indicates the two input modes ('a level or custom prompt'). It is clearly distinguishable from sibling tools like canvas or brush operations, though it does not explicitly name an alternative resegmentation path.

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?

It gives operational guidance on retry/reuse (reuse request_id, don't blindly retry outcome_unknown), which is real when-to-use guidance. However, it never states prerequisites such as balance/credits, authentication state, or which sibling to call to check job status or resolve an outcome_unknown.

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