Skip to main content
Glama
Sign In

Blender Bridge

by com.blenderbridge
OverviewDiscussionsAdmin

Set Desktop language

set_app_language
DestructiveIdempotent

Change the saved interface language of Blender Bridge Desktop on the receiving computer. language is one of the supported language codes. Use only when the user asks to change that interface; this is not a translation tool for scene content, project files or chat replies. Returns the Desktop control result. Use get_app_state to inspect the current language before changing it.

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": {
      "language": "<language>"
    },
    "name": "set_app_language"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageYesLanguage code to save for the receiving Desktop interface.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language / description
      Added value: +"Language code to save for the receiving Desktop interface."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare that this is a non-read-only, idempotent, destructive operation, so the description does not need to restate the safety profile. It adds useful context that the language setting is saved for the receiving Desktop, returns a Desktop control result, and should be preceded by get_app_state inspection. It does not clarify permissions or what 'destructive' means for this setting, which keeps it below a full 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?

The purpose is front-loaded, followed by parameter scope, usage exclusions, return behavior, and the prerequisite inspection step. The text is compact and every sentence contributes useful routing or scope information.

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?

With one required parameter, full schema coverage, rich annotations, and no output schema, the description provides enough to call the tool correctly. It covers purpose, usage boundaries, parameter meaning, expected return, and the recommended inspection step.

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?

The schema already has 100% description coverage and enumerates all supported language codes. The description adds only that language is one of the supported codes, which is slightly useful but does not add syntax or selection guidance beyond the schema.

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?

The description uses a specific verb and resource: it changes the saved interface language of Blender Bridge Desktop on the receiving computer. It also explicitly distinguishes the tool from translation of scene content, project files, or chat replies, and names get_app_state as the inspection tool.

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 states exactly when to use the tool: only when the user asks to change the Desktop interface language. It gives clear exclusions and names the alternative workflow, using get_app_state to inspect the current language before changing it.

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