Skip to main content
Glama

ai_modeling_local_edit

Refine a bounded region of a P2 3D model with your Studio account and a stable request_id. Reuse the same ID for retries; changed inputs conflict, and unknown outcomes must not be blindly retried.

Instructions

refine a bounded region of a P2 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_local_edit"
  }
}

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 declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description adds real behavioral value beyond that with idempotency semantics (reusing request_id returns the original job, changed input conflicts) and an explicit never-blindly-retry rule for outcome_unknown. It still does not say what the operation produces, whether the source model is mutated or a new operator is created, or how credit limits are enforced.

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 two facts that most affect correct invocation (account requirement, request_id reuse). Nothing is redundant, though the dense clause about request_id could be split for readability.

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, open-world, nested-parameter tool with no output schema and zero schema description coverage, the description covers idempotency and auth but leaves parameter meaning and outcome shape undocumented. It is adequate on safety semantics but incomplete on how to construct the call.

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% and the schema is nested, so the description carries the full explanatory burden, yet it only explains request_id. The bbox coordinate range (-1..1, two 3-element points), face_limit, max_estimated_credits, expected_operator_id (which looks like an optimistic-concurrency guard) and source_operator_id are all left 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?

"Refine a bounded region of a P2 model" gives a specific verb (refine) plus a scoped resource (a bounded region), which is more precise than a generic edit. It does not name or distinguish itself from plausible siblings such as ai_modeling_canvas_graph_edit or ai_modeling_segmentation_edit, and "P2 model" is unexplained jargon, so it stops short of a 5.

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 a prerequisite (a Studio account) and a retry policy for outcome_unknown, which is genuine usage context. However, it never states when to choose this local-edit tool over the sibling edit tools or what conditions make it inapplicable, so guidance remains implicit.

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