Skip to main content
Glama

ai_modeling_import_model

Imports an external model into a Studio workspace using your account and a stable request_id, so repeated requests return the original job and changed inputs are flagged as conflicts.

Instructions

import an external model into the Studio workspace. 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_import_model"
  }
}

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, openWorldHint=true, and destructiveHint=false. The description adds genuinely non-obvious behavior: idempotency semantics (reuse of a request_id returns the original job, changed input under the same id conflicts) and the instruction never to blindly retry an outcome_unknown result. It does not disclose credit consumption or what the returned job looks like, which keeps it from a 5.

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 with the action stated first and the risk guidance last, with no filler. The terseness costs some clarity: "outcome_unknown" is used as if the agent knows it is a job state, since no result schema defines it.

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?

The idempotency and no-blind-retry contract is the most important thing an agent needs, and it is present. But for a credit-spending mutation with a nested parameter object, no output schema, and 0% schema coverage, the description leaves the credit cap, the model_path format, and the shape of the returned job undefined.

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 carries the full burden, yet it only explains request_id (stability/idempotency) and gestures at a job-state field via "outcome_unknown." The other parameters — notably max_estimated_credits, a spend cap, plus model_path, name, use_original_uv, and the 16-element transform_matrix — get no meaning beyond their schema constraints. For a paid mutation with zero documented params, this is a significant gap.

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 gives a specific verb and resource: "import an external model into the Studio workspace." That is clearly distinguishable from siblings like ai_modeling_model_export or ai_modeling_model_generate without opening their schemas. It does not explicitly name a sibling or state the boundary case (e.g., import vs. generate), 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?

Usage is implied by "import an external model" and the requirement to use "your Studio account," but there is no explicit when-to-use versus alternatives guidance, nor any stated prerequisites such as authentication via ai_modeling_auth_begin. The retry guidance ("outcome_unknown must never be blindly retried") is operationally useful but governs retries rather than tool selection.

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