Skip to main content
Glama

ai_modeling_segment

Splits a 3D model into generated parts via your Studio account with a stable request ID. Reuse returns the original job; changed input conflicts, and unknown outcomes need safe handling.

Instructions

split a model into generated parts. 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_segment"
  }
}

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 declare readOnly=false, destructive=false and openWorld=true, so the safety profile is partly covered; the description adds materially beyond them by disclosing account/auth dependency, idempotency via request_id, deterministic conflict on changed input, and a distinct outcome_unknown state that must not be retried blindly. That is real failure-mode context an agent cannot get from annotations. It does not address cost consumption or latency despite the credit cap parameter.

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 clauses, front-loaded with purpose, then auth context, then idempotency rules; nothing is padded. The clipped, semicolon-chained style costs a little readability but wastes no words.

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 mutation tool with a nested parameter object, a required credit cap, and no output schema, the definition covers idempotency and one failure mode but leaves cost behavior, parameter choices, and result shape unexplained. An agent could invoke it but might set the credit cap or granularity arbitrarily.

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 parameter meaning; it explains request_id semantics well but says nothing about max_estimated_credits (a spend cap the caller must set) or any of the nested parameters fields: project_id, prompt, model_version, segmentation_granularity, expected_operator_id. Two of three top-level parameters and the entire nested object remain undocumented.

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?

"Split a model into generated parts" gives a concrete verb and resource, and the segmentation framing distinguishes it from the many download/list/auth siblings. It stops short of naming or contrasting any specific alternative, so an agent gets the action but must infer boundaries from names alone.

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 supplies operational rules (stable request_id, reuse returns the original job, changed input conflicts, outcome_unknown must not be blindly retried) but never states when to choose this tool over sibling modeling or canvas operations. Usage is implied by the verb rather than guided.

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