Skip to main content
Glama
Sign In

Blender Bridge

by com.blenderbridge
OverviewDiscussionsAdmin

Search public asset libraries

find_free_assets
Read-onlyIdempotent

Search free CC0 HDRIs, textures and models from Poly Haven and ambientCG without touching the scene, so the search adds no undo step. These are optional resources: searching does not request download or application. A chosen asset can be used in execute_blender_code with bb_get_asset and bb_use_hdri, bb_make_pbr_material or bb_import_model. Search words work best in English. Quote the asset's credit to the user: Poly Haven's terms require naming the source.

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": {
      "query": "<query>"
    },
    "name": "find_free_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoAsset category to search: HDRI, texture or model.
limitNoMaximum number of matching assets to return.
queryYesEnglish search terms for the desired asset.
sourceNoOptional public library filter: Poly Haven or ambientCG.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / kind / description
      Added value: +"Asset category to search: HDRI, texture or model."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of matching assets to return."
    • addedInput schema / properties / query / description
      Added value: +"English search terms for the desired asset."
    • addedInput schema / properties / source / description
      Added value: +"Optional public library filter: Poly Haven or ambientCG."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, but the description adds valuable behavior: no undo step is created, no download/application is requested, and Poly Haven credit must be shown to the user. These details materially improve transparency beyond the annotations.

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?

The description is front-loaded with the core action and keeps every sentence relevant to usage, behavior or follow-up steps. It is slightly longer than strictly necessary but does not waste space.

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?

Given the annotations and fully described schema, the description covers the key safety and usage context for a search-only tool. It could say more about the shape of returned asset results, but no output schema exists and the missing detail is minor.

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 description coverage is 100%, so query, kind, limit and source are already documented. The description only adds a mild search tip about English terms, which overlaps the schema's own query description, so baseline 3 is appropriate.

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: search free CC0 HDRIs, textures and models from Poly Haven and ambientCG. It also distinguishes the operation from scene-affecting tools by saying it works without touching the scene.

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?

Explains that these are optional resources, that searching does not download or apply anything, and that a chosen asset can then be used via execute_blender_code helpers. This gives clear usage context, though it does not explicitly list exclusions or alternatives.

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

All Blender Bridge toolsInspect
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