Blender Bridge

Decline collaboration invitation

decline_collaboration

DestructiveIdempotent

Refuse a pending collaboration invitation addressed to this account after the user requests it. id comes from incoming invitations in get_connection. Marks the invitation declined and returns refreshed connection state; does not accept or start shared-computer access. Use accept_collaboration if the user agrees to join, or end_collaboration to end an already pending/active session in which this account participates. view_decline_invitation is the app-panel adapter.

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": "decline_collaboration"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Incoming invitation identifier to decline, from connection state.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026
- addedInput schema / properties / id / description
```
Added value: +"Incoming invitation identifier to decline, from connection state."
```
First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, readOnly=false, so the safety profile is covered. The description still adds value beyond them: it discloses the concrete effect ('marks the invitation declined') and the return ('returns refreshed connection state'), plus the negative scope of what it does not do. It doesn't cover permission requirements or error cases, so not a 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?

Three sentences, front-loaded with the action and precondition, then effect, then alternatives. Each sentence carries distinct information (scope, behavior, routing) with no repetition of the title or 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?

No output schema exists, and the description compensates by stating the return shape ('refreshed connection state'), so the agent knows to re-read connection state after the call. What's missing is only peripheral — failure modes when the invitation is not pending, and whether other sessions are affected.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With one parameter at 100% schema coverage the baseline is 3, but the description adds provenance the schema lacks: 'id comes from incoming invitations in get_connection', telling the agent where to source the value rather than just its format.

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?

States a specific verb ('Refuse') applied to a specific resource ('a pending collaboration invitation addressed to this account') and pins the precondition ('after the user requests it'). It also explicitly negates a neighboring behavior ('does not accept or start shared-computer access'), which separates it from accept_collaboration without opening a 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?

Names the two competing actions and the condition selecting each: accept_collaboration 'if the user agrees to join', end_collaboration for 'an already pending/active session in which this account participates'. It also flags view_decline_invitation as the app-panel adapter, so the agent knows which surface to use.

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?