Skip to main content
Glama
Sign In

Blender Bridge

by com.blenderbridge
OverviewDiscussionsAdmin

Panel: accept collaboration

view_accept_invitation
Destructive

App-only adapter for the connection panel's Accept invitation button, after the user agrees to the displayed session role. id identifies an incoming invitation addressed to this verified account. For your_role=receive, supply an own listed device_id: this permits the other participant to control that computer. For your_role=control, no receiving computer is required from this account. Accepting changes session access and selection; returns updated connection state. Models should use accept_collaboration; use view_decline_invitation to refuse instead.

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": {
      "id": "<id>"
    },
    "name": "view_accept_invitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifier of the pending incoming invitation shown to this account.
device_idNoOwn listed receiving computer for accepting a receive-role invitation; unused when declining.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / device_id / description
      Added value: +"Own listed receiving computer for accepting a receive-role invitation; unused when declining."
    • addedInput schema / properties / id / description
      Added value: +"Identifier of the pending incoming invitation shown to this account."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds useful behavioral context: it requires prior user agreement, changes session access and selection, and returns updated connection state. It stops short of spelling out irreversibility or permission implications, but it adds meaningful context 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 adapter purpose and the routing instruction, and each sentence carries relevant information. It is somewhat dense, but none of the sentences are redundant given the role logic and sibling routing.

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?

For a two-parameter mutation adapter with no output schema, it covers the key gaps: prior user agreement, role-conditional device_id use, state changes, and the sibling alternative for decline. The main omission is explicit disclosure of whether the access change is reversible, though the annotations flag it as destructive.

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 both id and device_id are already documented in the input schema. The description adds the role-conditional relationship between your_role and device_id, but that is a modest addition over the schema's own 'receiving computer for accepting a receive-role invitation' wording.

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?

It states a specific verb and resource ('accept invitation', 'Accept invitation button') and immediately distinguishes itself as an app-only connection-panel adapter. It also names the model-facing sibling, accept_collaboration, so the tool's niche is unambiguous.

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 explicit routing: models should use accept_collaboration, and view_decline_invitation should be used to refuse. It also explains the role-dependent usage (your_role=receive requires an own device_id; your_role=control does not), which tells the agent exactly when this adapter applies.

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