Skip to main content
Glama

ai_modeling_uv_apply

Apply a completed UV candidate to a project's expected current model version by specifying the project and current/candidate operator IDs.

Instructions

Apply a completed UV candidate to the expected current model version.

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": {
      "project_id": "<project_id>",
      "current_operator_id": "<current_operator_id>",
      "candidate_operator_id": "<candidate_operator_id>"
    },
    "name": "ai_modeling_uv_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
current_operator_idYes
candidate_operator_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already tell the agent this is a non-read-only, non-destructive, open-world operation, so the safety profile is partly covered. The description adds almost nothing beyond that: it doesn't say whether applying overwrites the current model's UVs, whether the action is reversible, whether it fails if the model version has changed, or what permissions are needed. "Expected current model version" is suggestive of an optimistic-concurrency check but the behavior is never explained.

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?

A single front-loaded sentence with no filler or repetition. It is terse to the point of under-specification, but that is a completeness problem rather than verbosity.

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 three-parameter mutation with no output schema and no schema descriptions, the definition is thinner than the complexity warrants. The description does at least anchor the operation to a target model version, but key details needed to call it correctly — the role of the two operator IDs and the failure/modification semantics — are absent.

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% and the description explains none of the three required parameters. project_id is self-evident, but current_operator_id versus candidate_operator_id is genuinely ambiguous — the description does not clarify which is the source and which is the target, or the format/source of these identifiers.

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 ("apply") and resource ("a completed UV candidate") plus the target ("the expected current model version"), so the operation is identifiable. It does not differentiate itself from closely named siblings like ai_modeling_uv_commit, ai_modeling_uv_preview, or ai_modeling_model_metadata_apply, so an agent cannot tell from the text alone which one 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 Guidelines2/5

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

There is no explicit when-to-use guidance, no statement of the prerequisite pipeline (candidate must be generated/previewed first), and no mention of when not to use it or what alternative to choose. The word "completed" hints at a precondition but never states or verifies it.

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