Blender Bridge

Panel: decline collaboration

view_decline_invitation

DestructiveIdempotent

App-only adapter for the connection panel's Decline invitation button. id identifies a pending incoming invitation addressed to this verified account. Marks that invitation declined and returns refreshed connection state; does not accept access or start a shared session. device_id is not used for declining. Models should use decline_collaboration; end_collaboration is the separate action for ending an existing session.

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_decline_invitation"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Identifier of the pending incoming invitation shown to this account.
`device_id`	No	Own listed receiving computer for accepting a receive-role invitation; unused when declining.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

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."

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The annotations already declare destructive=true and idempotent=true, and the description adds useful context beyond them: it marks the invitation declined, returns refreshed connection state, and explicitly says it does not accept access or start a shared session. It also ties the invitation to a verified account, though it does not elaborate on reversibility or permission requirements beyond that.

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 app-only adapter role, then covers effect, non-effect, and alternatives. It is appropriately sized and mostly earns its sentences, though the id explanation slightly overlaps the schema.

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 mutation tool with rich annotations and full schema coverage, the description is complete enough: it explains the action, the return behavior, non-effects, and alternative tools. The only minor gap is that return-state details are summarized rather than fully specified, but no output schema is expected.

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 itself explains both parameters. The description reinforces that id must identify a pending incoming invitation for this verified account and that device_id is not used for declining, but it adds little beyond the already-complete parameter documentation.

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 states a specific action and resource: an app-only adapter that marks a pending incoming invitation as declined. It distinguishes this from siblings by explicitly naming decline_collaboration and end_collaboration, so an agent can separate this panel adapter from the general collaboration tools.

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 guidance: 'Models should use decline_collaboration' and 'end_collaboration is the separate action for ending an existing session.' It also clarifies that device_id is not relevant for declining, leaving little ambiguity about when and how this tool should be used.

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

All Blender Bridge tools Inspect

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

Need Help?