Skip to main content
Glama

ai_modeling_uv_generate

Generate or retry a UV candidate without applying it, using a stable request_id so repeated calls return the original job and changed inputs conflict safely.

Instructions

generate or retry a UV candidate without applying it. 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_uv_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes
max_estimated_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare it is a non-read-only, non-destructive, open-world call; the description adds genuinely non-obvious behavior: it authenticates against the Studio account and enforces idempotency via request_id (reuse returns the original job, changed input conflicts). The outcome_unknown warning is a real operational safeguard. It does not disclose credit consumption or the async job/result shape, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, no filler, with the scope constraint front-loaded and the idempotency and retry warnings ordered by importance. Every clause carries information an agent needs.

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 description covers the safety and idempotency model well, which is the core risk for this tool. However, with a nested parameter object, 0% schema coverage, no output schema and no annotation detail on side effects, it leaves the credit cap, operator-concurrency parameters, and return shape underexplained for a call that spends credits and creates server-side state.

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 must carry all meaning. It usefully explains request_id idempotency (reuse vs. conflict) and implies the action enum (generate/retry), but says nothing about max_estimated_credits (a budget cap on a credit-spending call) or project_id/current_operator_id/expected_operator_id (the optimistic-concurrency check). Two of three top-level parameters remain semantically opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair (generate/retry) and resource (UV candidate), and the clause 'without applying it' directly scopes it apart from ai_modeling_uv_apply. An agent can distinguish intent from siblings without opening any schema.

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?

Gives clear when-to-use context (create a candidate, or re-run a failed one, prior to applying) and a concrete when-not rule: 'outcome_unknown must never be blindly retried.' It stops short of naming the apply/preview siblings to route to, but the exclusions it does state are actionable.

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