R3

Show your work in progress on the Blender page

r3_blender_draft_push

While you build a model in Blender for the user, push an APPLIED copy of your working .blend after each step (body done, wheels done, materials done): the user's Blender page shows it as a 3D preview they can orbit. A draft is not a saved version: one draft per user, the newest wins, kept 24 hours. Answers a one-time ticket (5 minutes) and the draft endpoint (URL, method, Authorization header; the body is the file's raw bytes); sending it needs file access where the .blend is. The draft is a copy with its modifiers applied and its textures packed; r3_blender_upload saves the real file once the user is happy. Up to 20 MB. Needs the blender:upload right.

Input Schema

Name	Required	Description	Default
`model`	Yes	The model's name, as the page shows it: "monster-truck" (the same name you will save it under).

Output Schema

Name	Required	Description
`url`	Yes
`body`	Yes
`model`	Yes
`answer`	Yes	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.
`method`	Yes
`ticket`	Yes
`headers`	Yes
`maxBytes`	Yes
`expiresAt`	Yes
`environment`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 16, 2026

addedOutput schema / properties / body
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / curl

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / headers

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "Authorization": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "Authorization"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "ticket",
-  "url",
-  "method",
-  "curl",
-  "expiresAt",
-  "maxBytes",
-  "environment",
-  "model",
-  "answer"
-]New value: +[
+  "ticket",
+  "url",
+  "method",
+  "headers",
+  "body",
+  "expiresAt",
+  "maxBytes",
+  "environment",
+  "model",
+  "answer"
+]

AddedOct 16, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations cover the safety profile, but the description goes well beyond them: one draft per user, newest-wins, 24-hour retention, 20 MB limit, required blender:upload right, and a one-time ticket (5-minute) plus endpoint/auth mechanics. It also clarifies the copy is modifiers-applied and textures-packed, which matters for what the user sees.

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?

Front-loaded with the core behavior and each clause carries real information. It is dense and slightly run-on with parenthetical ticket/endpoint detail, but there is little waste.

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

Completeness5/5

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

Covers retention, size limit, auth requirements, the ticket/endpoint delivery, and the contrast with the save path. With an output schema present, return values need not be described, so the definition is complete for correct invocation.

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

Parameters3/5

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

Schema coverage is 100% and the single 'model' parameter is already fully documented in the schema, so the description carries no additional parameter meaning. Baseline 3 applies when the schema does the heavy lifting.

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 and resource (push an applied copy of the working .blend as a draft) and immediately distinguishes it from the sibling r3_blender_upload, which 'saves the real file.' An agent can tell exactly what this does and how it differs from the nearest alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly states when to invoke it ('after each step: body done, wheels done, materials done') and when the sibling is the right choice instead ('r3_blender_upload saves the real file once the user is happy'). Nothing is left to inference.

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

All R3 tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?