Blender Bridge

Panel: prepare file download

view_download

App-only adapter for the file panel's Download and Reveal controls. path is a workspace-relative result selected in that panel. action defaults to download: remote delivery uploads the requested existing file and returns a temporary download link in view.download; treat that link as bearer access to the result. reveal shows a validated local file in its containing folder when supported and returns view.reveal. Does not render or save a new scene. Models should use get_project_file for delivery, or list_project_files to discover existing outputs.

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": {
      "path": "<path>"
    },
    "name": "view_download"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Workspace-relative result path selected in the panel file list.
`action`	No	download prepares file delivery; reveal shows a validated local file in its containing folder when supported.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedInput schema / properties / action / description

Added value: +"download prepares file delivery; reveal shows a validated local file in its containing folder when supported."

addedInput schema / properties / path / description

Added value: +"Workspace-relative result path selected in the panel file list."

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, but the description adds context those flags cannot convey: the returned link in view.download behaves as bearer access to the result, and reveal only works 'when supported.' That security and conditional-availability note is genuinely non-obvious. It stops short of saying anything about link expiry or failure modes, so not a 5.

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?

Five tight sentences ordered purpose → behavior → scope exclusion → alternative routing, with the most decision-relevant line (use get_project_file instead) placed last as a clear exit. No filler or restated schema text.

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?

With no output schema, the description correctly compensates by naming the return keys (view.download, view.reveal), and it covers both parameters and the app-only constraint. It omits error behavior for an unsupported reveal or for a path outside the workspace, which would matter for a tool with min/max path constraints.

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 both parameters are documented in-schema, so the baseline is 3. The description does add two useful facts beyond the schema – that 'action defaults to download' and precisely what each action returns (view.download vs view.reveal) – which keeps it at the baseline rather than below.

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 lead sentence identifies the resource (the file panel's Download and Reveal controls) and the following sentences describe the concrete effect: upload the existing file and return a temporary link in view.download, or reveal a validated local file. That is enough for an agent to distinguish it from get_project_file and list_project_files. The only softness is that the opening 'app-only adapter' framing is abstract and the actual verb+effect only becomes clear in sentence two.

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?

It explicitly routes the agent away: 'Models should use get_project_file for delivery, or list_project_files to discover existing outputs,' naming two concrete alternatives and their selecting conditions. It also bounds scope with 'Does not render or save a new scene.' When-to-use vs when-not is fully covered.

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

All Blender Bridge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?