Skip to main content
Glama

remove_client

Destructive

End the coaching relationship with a client (confirm-gated). This does not delete the client's account or history — it only disconnects them from this coach. Irreversible from this tool; the client would need to re-request or be re-invited.

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": {
      "clientId": "<clientId>"
    },
    "name": "remove_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
clientIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, yet the description still adds real information: the confirm gate produces a preview when unset, the blast radius stops at the coach-client link, and reversal requires re-request/re-invite. It does not describe secondary effects on habits, check-ins, or messaging that belong to the removed relationship, which keeps it from 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.

Conciseness5/5

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

Three short clauses, front-loaded with the action and the confirm gate, then the scope boundary, then irreversibility. Every sentence carries decision-relevant information and none repeats the name or annotations verbatim.

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, two-parameter tool with no output schema, the definition covers safety gating, destruction scope, and reversibility. It omits what the preview returns and whether dependent records (habits, check-ins) are affected, which are the remaining gaps for an irreversible action.

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 50% and the one documented parameter (confirm) already explains the preview behavior, so "(confirm-gated)" largely restates it. For clientId the description only implies "the client" being disconnected, adding modest meaning beyond the bare string schema. Baseline 3 fits given the partial coverage.

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?

"End the coaching relationship with a client" gives a specific verb and resource, and the following clause explicitly bounds the scope against the nearest read of the name (account/history deletion). An agent can distinguish this from the delete_* client tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Usage context is clear: this is the tool for terminating a coach-client link, and the description explains the re-invite path when the decision is reversed. It stops short of naming an alternative tool or stating prerequisites (owner/admin permissions, whether the coach must be the caller), so it is clear but not fully exclusionary.

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.