Skip to main content
Glama

ai_modeling_complete

Complete or cap selected model parts through your Studio account using a stable request_id; reuse returns the original job, while changed input conflicts and uncertain outcomes must not be retried blindly.

Instructions

complete or cap selected model 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_complete"
  }
}

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
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds genuinely useful behavior: it consumes the Studio account, is idempotent per request_id, returns the original job on reuse, and conflicts on changed input. It omits credit consumption despite a max_estimated_credits parameter, and says nothing about what happens to parts that are not selected.

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 operational constraints. Slightly telegraphic lowercase phrasing, but no sentence 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?

For a mutating, credit-consuming, nested-parameter tool with no output schema, the description covers auth and idempotency but leaves cost semantics, part selection defaults, and result shape unaddressed. Adequate to avoid duplicate-job mistakes, not complete enough to call confidently.

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% across three required parameters plus a nested object, so the description must compensate. It does explain request_id semantics well and its "complete or cap" phrasing hints at the completion_mode enum, but max_estimated_credits, project_id, part_names (default empty) and expected_operator_id are left entirely to the schema.

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 pair and resource: "complete or cap selected model parts." That is concrete enough to distinguish it from sibling tools like brush_paint or canvas_create, though it never names an alternative or explicitly scopes which parts are eligible.

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?

Usage is only implied through the idempotency rules (reuse request_id, don't blindly retry outcome_unknown). There is no explicit statement of when to choose ai_completion versus quick_cap, or when to prefer a different sibling tool for non-part operations.

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