Skip to main content
Glama

ai_modeling_modification

Saves per-triangle segment labels and part names from inline arrays or a bound segmentation state file, using a stable request ID to keep Studio modification jobs idempotent.

Instructions

save per-triangle segment labels and names from inline arrays or a bound segmentation state file. 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_modification"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes
max_estimated_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only say this is a non-read-only, non-destructive, open-world call; the description adds real behavior on top of that — account binding, idempotency via request_id, conflict semantics on changed input, and explicit retry rules for outcome_unknown. It does not explain credit consumption despite the required max_estimated_credits cap, which is the main remaining behavioral gap.

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 tight sentences, front-loaded with the core operation before the idempotency caveats; no filler. A little more explanatory phrasing around 'outcome_unknown' would help without bloating it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter write tool with a nested object and no output schema, the description covers purpose, input alternatives, idempotency, and failure handling well. The gaps are the unexplained credit cap and the absence of any note on what the returned job contains, which matters since no output schema exists.

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 reported at 0%, so the description must carry parameter meaning; it partially does by mapping 'inline arrays' and 'bound segmentation state file' onto the part_indices/part_indices_name versus indices_path inputs, and by calling request_id a stable idempotency key. It says nothing about max_estimated_credits (spend cap semantics) or project_id/expected_operator_id, leaving a required parameter entirely unexplained.

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 names a specific verb and resource: saving per-triangle segment labels and names, with two supported input modes (inline arrays or a bound segmentation state file). An agent can tell exactly what the tool does, though it never contrasts itself with sibling tools such as brush operations that also write segment data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states the two ways to supply data (inline arrays vs. a bound segmentation state file) and gives strong retry discipline: reuse of a request_id returns the original job, changed input conflicts, and outcome_unknown must not be blindly retried. What is missing is any statement of when to prefer this over sibling tools or any prerequisite/ordering guidance.

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