Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_delete_member

DestructiveIdempotent

Removes a member's access to an account, with a safeguard preventing removal of the account's last OWNER.

Instructions

Removes a member's access to the account. The account's last OWNER cannot be removed.

BeeL API endpoint: DELETE /v1/accounts/{account_id}/members/{member_id} (reference: https://docs.beel.es)

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": {
      "account_id": "<account_id>",
      "member_id": "<member_id>"
    },
    "name": "beel_delete_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
member_idYesMembership unique UUID.
account_idYesYour own account, or an account you provisioned. It — not the credential — decides which account the operation acts on; a `403` is returned when you do not reach it, the same response an account that does not exist gets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.3.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds a genuine business rule beyond annotations: the last OWNER is protected from removal, which signals an error path an agent should anticipate. It stops short of saying whether the member's grants are cascaded or removed.

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 core behavior and the OWNER constraint are front-loaded in two tight sentences, and the endpoint reference is compact. The docs URL and endpoint restatement add marginal value but are not wasteful.

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 and full parameter documentation in the schema, the description needs only to cover behavior and pitfalls, and it covers the key destructive-case constraint. Missing details such as cascade effects on member grants or required auth role keep it from being fully complete with a destructive mutation.

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 both parameters are fully documented in the schema, including the account_id scoping/403 behavior. The description only echoes the two path parameters through the endpoint line, adding no new meaning; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: it removes a member's access to the account, which is distinct from the sibling beel_delete_member_grant (grants) and beel_patch_member (editing). It does not explicitly contrast itself with those siblings, but the resource 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states one important precondition — the account's last OWNER cannot be removed — which helps an agent avoid a failing call. However, it never says when to use this versus beel_delete_member_grant or beel_patch_member, nor what permission level is required to perform the removal.

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

Deploy Server

Other Tools