Skip to main content
Glama

ai_modeling_copy

Save a model version as a new Studio project using a stable request_id; reuse returns the original job, changed input conflicts, and unknown outcomes need verification before retrying.

Instructions

save a model version as a new Studio project. 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_copy"
  }
}

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 substantial context beyond that: account binding, idempotency via a stable request_id, reuse returning the original job, conflict on changed input, and the 'outcome_unknown' state that must not be blindly retried. It stops short of covering credit consumption implied by max_estimated_credits or what happens to the source model version, so it is strong but not complete.

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 front-loaded sentences with no filler; the core action comes first and the idempotency rules follow in priority order. Sentence fragments ('changed input conflicts') are terse to the point of slight ambiguity but not wasteful.

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 tool with no output schema and a nested parameters object, the description covers the risky idempotency semantics well but leaves the bulk of the input contract unexplained — no meaning for project_id, operator_id, or max_estimated_credits, and no indication of what the returned job actually contains.

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% across three required parameters, so the description carries the full burden. It only explains request_id (stable, reused, conflict on change); the nested parameters.project_id and parameters.operator_id are never described, and max_estimated_credits — a cost guardrail with a 0-100000 bound — is not explained at all despite being a required parameter.

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 states a specific verb and outcome: 'save a model version as a new Studio project', which tells an agent exactly what is produced (a new Studio project from a model version). It does not name or differentiate itself from any sibling (e.g. canvas_create or canvas_from_template), so an agent must infer from the name alone which creation-style tool to pick.

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 guidance is limited to retry semantics ('reuse returns the original job', 'changed input conflicts', 'outcome_unknown must never be blindly retried'), which is genuinely useful operational guidance. However, there is no statement of when to choose this over other project/canvas creation siblings, nor prerequisites such as authentication or credit requirements beyond the passing mention of a Studio account.

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