Skip to main content
Glama

Update projects to a Blender model's current version

r3_blender_update
Destructive

A re-uploaded Blender model is always its latest version; the user's projects keep the meshes they have until asked. This tool asks and answers that one question: choice update_projects without reportId shows which projects and entity templates use an older version (or an earlier import of the same file) and what changed; with the reportId and the projectIds / entityTemplateIds the user chose, it moves just those to the current version. Which ones move is the user's choice; "not now" means no call. Parts are matched by Blender OBJECT name: each takes its new mesh and placement; when only its shape changed it keeps the project's materials and the edits made to them in R3; when its materials changed in Blender it takes Blender's materials where the import's own material is unchanged, while a material made or changed in R3 is kept unless the user chooses Blender's (replaceMaterials, from the plan's materialChoices), and a material made in R3 is never deleted. Objects new in the model are added under the copy's root Empty, parts the model no longer has are kept (removeGone: true removes them). Published releases never change. The plan only reads; moving projects needs the blender:update right.

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": {
      "blenderModelId": "<blenderModelId>",
      "choice": "<choice>"
    },
    "name": "r3_blender_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
choiceYesRequired: update_projects. There is no default.
reportIdNoThe report being answered, from the plan (this tool without reportId). Leave it out to plan.
projectIdsNoWith a reportId: the projects to update.
removeGoneNoAlso remove the parts the current version no longer has (default false: they are kept and listed). Plan with it and answer that report with it.
blenderModelIdYesThe Blender model, from r3_blender_list.
replaceMaterialsNoWith a reportId: material ids from the plan's materialChoices (materials made or changed in R3, kept by default) the user chose to replace with Blender's. Default none: R3's materials are kept.
entityTemplateIdsNoWith a reportId: the entity templates to update.

Output Schema

NameRequiredDescriptionDefault
keptYes
liveNo
answerYesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.
choiceYes
reportIdNo
freedRowsYes
repointedYes
duplicatesNo
environmentYes
projectPartsNo
currentFileIdYes
versionNumberNo
blenderModelIdYes
materialChoicesNo
behindProjectIdsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / replaceMaterials
      Added value: +{
      +  "description": "With a reportId: material ids from the plan's materialChoices (materials made or changed in R3, kept by default) the user chose to replace with Blender's. Default none: R3's materials are kept.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / materialChoices
      Added value: +{
      +  "items": {},
      +  "type": "array"
      +}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / projectParts
      Added value: +{
      +  "items": {},
      +  "type": "array"
      +}
    • addedOutput schema / properties / versionNumber
      Added value: +{
      +  "type": "number"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / properties / removeGone
      Added value: +{
      +  "description": "Also remove the parts the current version no longer has (default false: they are kept and listed). Plan with it and answer that report with it.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / duplicates
      Added value: +{
      +  "items": {},
      +  "type": "array"
      +}
  4. Changed1 schema field changed
    • addedOutput schema / properties / behindProjectIds
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  5. Changed2 schema fields changed
    • addedOutput schema / properties / answer
      Added value: +{
      +  "description": "This answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "blenderModelId",
      -  "choice",
      -  "currentFileId",
      -  "repointed",
      -  "kept",
      -  "freedRows",
      -  "environment"
      -]New value: +[
      +  "blenderModelId",
      +  "choice",
      +  "currentFileId",
      +  "repointed",
      +  "kept",
      +  "freedRows",
      +  "environment",
      +  "answer"
      +]
  6. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only say destructiveHint=true, readOnlyHint=false, openWorldHint=true, idempotentHint=false; the description adds far more, including the permission needed (blender:update), that published releases never change, that unmatched parts are kept unless removeGone is true, that R3-made materials are never deleted, and how object names drive matching. These are exactly the mutation consequences an agent needs before invoking a destructive tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The content is valuable but delivered as one dense block with semicolon-chained clauses and parenthetical asides, so the two-mode structure is buried mid-paragraph. Front-loading the plan/apply distinction ahead of the material-merging detail would make it far easier to parse. Little of the text is wasted, but the structure costs readability.

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

Completeness4/5

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

For a 7-parameter destructive tool with an output schema and full annotation coverage, the description supplies modes, defaults, permission requirements, and material/object edge cases. What remains unstated is minor, such as report staleness or error behavior, which the output schema can reasonably carry.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by explaining the relationship between the plan call and reportId, where replaceMaterials ids come from (the plan's materialChoices), and what removeGone actually removes. The material-matching rules give real meaning to replaceMaterials that the schema alone does not convey.

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 establishes a specific verb+resource: it moves the user's chosen projects (and entity templates) to a Blender model's current version, and it explicitly covers both modes (plan without reportId, apply with reportId). It distinguishes the tool from the import/upload siblings by scoping it to updating existing projects. The opening sentence is domain background rather than a direct statement of what the tool does, which slightly delays the purpose.

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?

Clear when-to-use guidance: call without reportId to get the plan of what is outdated, then call again with reportId plus projectIds/entityTemplateIds to apply. It also gives a when-not: "'not now' means no call," and notes the plan only reads while moving requires the blender:update right. It does not compare itself to adjacent tools such as r3_blender_import, but the two-step workflow is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources