Skip to main content
Glama
Sign In

Blender Bridge

by com.blenderbridge
OverviewDiscussionsAdmin

Invite a collaboration participant

invite_collaborator
Destructive

Start a bounded session by email or confirmed friend. role=control (default) requests using the recipient's Blender and requires no computer on the sender. role=receive offers your own listed device_id. The recipient sees the opposite role and accepts once. Roles apply only to this session; friendship never grants access.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "invite_collaborator"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNocontrol requests the recipient's Blender; receive offers this account's own receiving computer.
emailNoRecipient account email when inviting by address rather than friend_id.
device_idNoOwn listed computer offered for role=receive; use an identifier returned by account computer discovery.
friend_idNoConfirmed friend identifier from list_friends, as an alternative to email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. Changed4 schema fields changed
    • addedInput schema / properties / device_id / description
      Added value: +"Own listed computer offered for role=receive; use an identifier returned by account computer discovery."
    • addedInput schema / properties / email / description
      Added value: +"Recipient account email when inviting by address rather than friend_id."
    • addedInput schema / properties / friend_id / description
      Added value: +"Confirmed friend identifier from list_friends, as an alternative to email."
    • addedInput schema / properties / role / description
      Added value: +"control requests the recipient's Blender; receive offers this account's own receiving computer."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the mutation/non-idempotent/open-world profile, and the description adds genuinely new behavioral context: the recipient sees the opposite role, accepts exactly once, and role scope is limited to this session with friendship conferring no access. It omits lifetimes/expiry and what state the invite leaves behind on failure.

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?

Four short sentences, front-loaded with the action and the role branch before the lower-priority caveats about session scope and friendship. Dense but no filler; a slight cost is the unexplained jargon 'bounded session'.

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

Completeness3/5

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

For a destructive, non-idempotent invite with no output schema, the description says nothing about what is returned (an invite id?) or how to track the pending invitation (e.g. view_session_state). It also never names accept_collaboration/decline_collaboration as the recipient-side follow-ups, leaving the agent to infer the workflow.

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 schema already describes role, email, device_id, and friend_id in comparable terms, so most of the description's role explanation is redundant. The one real addition is that role defaults to 'control' and that control requires no local computer, but the email/friend_id mutual exclusion is never made explicit.

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?

States a specific verb and resource ('Start a bounded session by email or confirmed friend') and immediately scopes it to the two invite channels. It is distinguishable from siblings such as accept_collaboration or end_collaboration, though it never names the counterpart tool the recipient would use.

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?

Gives clear selection logic for the main branching decision: role=control (default) requests the recipient's Blender and requires no local computer, whereas role=receive offers your own listed device_id. It does not state when to prefer email over friend_id, nor when to use a different collaboration tool instead.

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