Blender Bridge

Panel: manage friend

view_manage_friend

Destructive

App-only adapter for the panel's friend-request and contact-management buttons. action=request uses email; accept, decline and remove use the relevant contact/invitation id. Can send a request or change a contact relationship after the user chooses the action. Returns updated contact state; grants no Blender-session access. Models should use manage_friend, and invite_collaborator for an actual shared Blender 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": {
      "action": "<action>"
    },
    "name": "view_manage_friend"
  }
}

Input Schema

Name	Required	Description
`id`	No	Existing friend or invitation identifier for accept, decline or remove, from the returned contact state.
`email`	No	Recipient account email for action=request.
`action`	Yes	Request a new friendship, accept or decline an invitation, or remove an existing friend.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

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,}$"

Changed3 schema fields changedOct 23, 2026

addedInput schema / properties / action / description

Added value: +"Request a new friendship, accept or decline an invitation, or remove an existing friend."

addedInput schema / properties / email / description

Added value: +"Recipient account email for action=request."

addedInput schema / properties / id / description

Added value: +"Existing friend or invitation identifier for accept, decline or remove, from the returned contact state."

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds real context beyond them — that it returns updated contact state and 'grants no Blender-session access' — which prevents a common misreading with the similarly named collaboration tools. It stops short of saying whether a removal is reversible or what failure looks like, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the adapter role and routing guidance, then parameter mapping, then the access caveat — a sensible order. The sentence 'Can send a request or change a contact relationship after the user chooses the action' largely restates the action enum and is the one line that doesn't fully earn its place.

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 does note the return value ('Returns updated contact state') plus the security boundary, which is enough to call it correctly. For a destructive mutation it could still say whether removing a friend is reversible or what happens if the id is stale, so it falls just short of complete.

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?

Schema coverage is 100% and the enum is described, so the baseline is 3. The description earns above baseline by summarizing the action→parameter mapping ('action=request uses email; accept, decline and remove use the relevant contact/invitation id') in one place, saving the agent from cross-reading two schema fields to understand which parameter is live for which action.

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+resource ('App-only adapter for the panel's friend-request and contact-management buttons') and enumerates the four actions it covers. It explicitly names the siblings it is not: manage_friend for model use and invite_collaborator for actual Blender sessions, so an agent can pick it apart from the crowded collaboration tool set.

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?

Explicit routing guidance: 'Models should use manage_friend, and invite_collaborator for an actual shared Blender session,' which names both alternatives and the condition selecting each. It also scopes per-action parameter usage (request→email, accept/decline/remove→id), leaving no ambiguity about when this adapter is appropriate.

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?