Skip to main content
Glama

Remove client seat

remove_client_seat
Destructive

Remove one paid client seat, lowering the bill (the dashboard's Remove a seat). When every seat is in use, name the client to switch off: it is locked, not deleted, and the others keep their seats. A client on its own bill runs to the end of the month it paid for; otherwise the plan drops a seat now, with unused time credited unless a bill is still unpaid. Call without confirm to preview and show the person the result, then confirm: true after they agree. Adding seats charges a card: give the Billing link from account_links instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "remove_client_seat"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.
switch_offNoThe client to switch off, by name from list_clients. Without it, the last-ranked client holding a seat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/readOnlyHint annotations by explaining the actual consequence: the client is "locked, not deleted," other clients keep seats, and billing behaves differently for own-bill clients (runs to month end) versus shared plans (drops a seat now with prorated credit unless a bill is unpaid). It also discloses the two-step preview/confirm safety pattern.

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 operation and its billing effect, then the branching cases, then the confirm workflow, then the cross-sell routing. Dense but every sentence carries information; the parenthetical UI anchor and the final billing-link sentence are slightly incidental but still useful for an agent talking to a user.

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, non-idempotent operation with no output schema, the description covers consequences, reversibility (lock vs delete), billing proration edge cases, and the preview mechanism. Nothing an agent needs before calling is missing.

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; the description adds the triggering condition for switch_off (only relevant when every seat is in use) and reinforces the preview-then-confirm protocol for confirm. It stops short of adding format or naming details for switch_off, which the schema already handles.

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 ("Remove one paid client seat, lowering the bill") plus the UI anchor ("the dashboard's Remove a seat"), so an agent knows exactly which operation this is. It also implicitly distinguishes itself from seat-adding, which no sibling name alone would convey.

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 concrete when-to-use conditions: pass switch_off only when every seat is in use, and call with confirm=false first to preview then confirm=true after user agreement. It also routes the opposite need elsewhere ("Adding seats charges a card: give the Billing link from account_links instead").

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.