Skip to main content
Glama
Sign In

Blender Bridge

by com.blenderbridge
OverviewDiscussionsAdmin

Panel: invite participant

view_invite_collaborator
Destructive

App-only adapter for the panel's Invite participant control. Creates a session invitation to email or friend_id. role=control requests the recipient's Blender; role=receive offers this account's listed device_id. The recipient must approve before shared access is active. Returns invitation/session state. Models should use invite_collaborator rather than this panel adapter.

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": "view_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

A4.3/5.0
Behavior4/5

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

Beyond annotations, it discloses the approval gate ('The recipient must approve before shared access is active') and the return shape ('Returns invitation/session state'), which materially change how an agent should treat the result. It stops short of explaining why destructiveHint=true applies to an invitation tool or what auth/session prerequisites exist, so it is not fully exhaustive.

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 identity and the alternative-tool warning, and every sentence carries routing or behavioral information. There is mild redundancy: the role semantics are restated from the schema, costing a little 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?

With no output schema, the description usefully states what is returned, and it covers the approval lifecycle that an agent needs to set expectations. For a destructive, non-idempotent, open-world mutation, it could add a note on reversibility or cancellation (e.g., view_end_collaboration), leaving a small gap.

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%, so all four parameters are already documented in the schema. The description's role=control/role=receive sentence largely restates the enum description rather than adding format, constraint, or interplay guidance (e.g., email vs friend_id exclusivity). Baseline 3 applies.

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 names a specific verb and resource ('Creates a session invitation') and immediately scopes it as an 'App-only adapter for the panel's Invite participant control,' which distinguishes it from the general invite_collaborator sibling. An agent can tell what it does and which control it mirrors without opening the schema.

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 gives an explicit routing instruction: 'Models should use invite_collaborator rather than this panel adapter.' That states both when this tool is the wrong choice and what to use instead, which is the strongest form of usage guidance.

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