Skip to main content
Glama

Remove a member

company_member_remove
DestructiveIdempotent

Removes another member from one of your companies; their access ends immediately. Owners can remove anyone; admins only members and viewers. You cannot remove yourself (use company_leave) and a company keeps at least one owner. Call without confirm first for a preview, then again with confirm and the preview_token.

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": {
      "company": "<company>",
      "member": "<member>"
    },
    "name": "company_member_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
memberYesMember ref (MB-XXXXXXXX) from company_members_list.
companyYesCompany ref (CO-XXXXXXXX) from company_list_mine.
confirmNoSet true only on the second call, after the user approved the preview.
preview_tokenNoThe preview_token returned by the first call (same input).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=false, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that — immediate access revocation, role-based authorization limits, the last-owner invariant, and the preview/confirm handshake. However, it does not say whether the preview_token expires or what the preview returns, which leaves a behavioral gap for a destructive operation.

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 tight sentences: what it does and its immediate effect first, authorization rules second, the required call protocol last. No redundancy and nothing buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, four-parameter mutation with no output schema, the definition covers effect, permissions, invariants, exclusions, and the two-step confirmation requirement — enough for an agent to call it correctly and safely without further inference.

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 each field already documents itself, including the confirm and preview_token semantics. The description still adds value by framing them as a sequence ("Call without confirm first for a preview, then again with confirm and the preview_token"), which the schema states only per-field. It does not add format or constraint detail beyond that.

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 and resource ("Removes another member from one of your companies") and immediately scopes the effect ("their access ends immediately"), which separates it from company_leave, the self-service sibling it names directly.

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?

Gives explicit authorization tiers (owners can remove anyone; admins only members and viewers), two hard exclusions (cannot remove yourself — use company_leave; a company keeps at least one owner), and the exact two-call confirmation protocol. An agent knows both when to call it and when it will be refused.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources