Skip to main content
Glama

ai_modeling_retexture_get

Read-only

Retrieve and inspect the generated Magic Brush preview for an operator ID to verify retexture output before proceeding.

Instructions

Inspect the generated Magic Brush preview.

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": {
      "operator_id": "<operator_id>"
    },
    "name": "ai_modeling_retexture_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
operator_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered without help. The description adds only the word "generated," implying a prior generation step, but says nothing about what happens if no preview exists, whether the result is an image/URL/metadata, or whether the preview is transient. Beyond the annotations, the added context is minimal.

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 short sentence with the resource front-loaded and no filler. It is efficient, though the brevity edges into under-specification rather than tightness. Nothing is wasted, but not much is delivered either.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining return values, and it does not. The single required parameter is undocumented, and there is no guidance on preconditions or failure modes. For a tool whose entire value is the retrieved preview, this leaves the agent calling blind.

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?

There is one required parameter, operator_id, and schema description coverage is 0% — the schema supplies only a regex pattern and length bounds, no meaning. The description never mentions the parameter at all, so an agent gets no explanation of what an operator_id identifies or where to obtain it. With coverage this low, the description should compensate and does not.

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

Purpose3/5

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

The description pairs a verb ("Inspect") with a resource ("the generated Magic Brush preview"), so the general intent is graspable. However, "inspect" is vague about what is actually returned, and it gives no signal distinguishing it from nearby siblings such as ai_modeling_retexture_images or ai_modeling_retexture_apply. An agent knows roughly what domain it is in but not exactly what this call yields.

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 statement of when to call this versus the retexture/images/apply siblings, and no prerequisites are given. The word "generated" hints that a preview must already exist, but this is left implicit rather than stated. An agent must guess at the correct sequencing.

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