Skip to main content
Glama

Leave a company

company_leave
DestructiveIdempotent

Leaves one of your companies; your access ends immediately and you need a new invitation to return. The last owner cannot leave: make someone else an owner first. 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>"
    },
    "name": "company_leave"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
Behavior5/5

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

Annotations already declare destructive=true and non-readonly, but the description adds the operational consequences an agent cannot get from those flags: access ends immediately, rejoining requires a fresh invitation, and the last-owner block. The preview/confirm handshake is also disclosed, which materially affects how the tool must be invoked.

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 short sentences, front-loaded with the effect of the call, then the blocker, then the procedure. No sentence is filler and the most decision-relevant information comes first.

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 destructive, non-idempotent-looking mutation with no output schema, the description covers consequences, preconditions, and the required two-call sequence. The only gap is what the preview step actually returns, which an agent would need to reason about the confirmation flow.

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%, so the baseline is 3, and the description goes slightly beyond it by framing confirm and preview_token as a paired second-call flow rather than isolated flags. It does not add parsing detail for the company ref beyond what the schema's pattern and description already supply.

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?

"Leaves one of your companies" is a specific verb plus resource with an immediate stated consequence ("your access ends immediately"), so an agent can tell this is a self-removal rather than an admin action like company_member_remove. It stops short of naming any sibling outright, leaving the distinction to inference from "your companies".

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 an explicit precondition (the last owner cannot leave; promote someone first) and an explicit call sequence (preview first without confirm, then again with confirm and preview_token). The when-not case and the required two-step procedure are both spelled out rather than implied.

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