Skip to main content
Glama

Remove a cashier

revoke_cashier
DestructiveIdempotent

Removes a cashier’s access (or cancels an invite). It takes effect on their next request. The owner can’t be removed.

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

Input Schema

NameRequiredDescriptionDefault
member_idYesFrom list_team

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 safety is covered. The description adds behavior the annotations cannot express: the change is deferred ('takes effect on their next request') and a protected-account guard ('owner can't be removed'), both of which materially shape how an agent should sequence and verify the call.

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 with no waste: the action first, then the timing effect, then the failure guard. Each sentence carries distinct operational information and nothing is repeated from the title or schema.

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 one-parameter destructive mutation, the definition covers purpose, timing, and the key failure condition, while annotations carry the safety profile and no output schema is needed. The only small gap is what the caller gets back (confirmation vs. no content), which is minor here.

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?

There is a single required parameter with 100% schema coverage, and the schema already documents that member_id comes from list_team. The description adds no additional meaning about the identifier (format, whether an invite id is accepted), so the baseline of 3 for high-coverage schemas applies.

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 opens with a specific verb and resource ('Removes a cashier's access') and clarifies that the same call also cancels a pending invite, so the agent understands the scope covers both active members and invitations. It does not explicitly name invite_cashier as the inverse operation, but the verb+resource pairing is unambiguous enough for selection.

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?

It supplies a concrete usage constraint ('The owner can't be removed') that tells the agent when this call will fail, which is real guidance rather than filler. It stops short of naming an alternative tool for related state changes, so it lands at clear context with one explicit exclusion rather than full when/when-not routing.

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