Skip to main content
Glama

Sign everyone out of an app

appSharingSignOutEveryone
Destructive

Sign everyone out of one of your apps, so they have to get in again. Requires confirmed: true, representing the human’s agreement.

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": {
      "projectId": "<projectId>",
      "confirmed": "<confirmed>"
    },
    "name": "appSharingSignOutEveryone"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmedYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
stateYes
messageYes
outcomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is largely carried by structured data. The description adds genuinely useful context beyond that — everyone loses their session and must sign in again, and an explicit human confirmation is required — but says nothing about reversibility, timing of the sign-out, or any limits on how many sessions are affected.

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?

Two short sentences with zero padding; the action and its effect come first and the hard prerequisite follows. Every clause carries information the agent needs.

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 two-parameter destructive action with an output schema and full annotation coverage, the description supplies what remains: the blast radius (all users), the consequence (must sign in again), and the mandatory human-confirmation gate. Return values need not be explained because an output schema exists.

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 description coverage is 0%, so the description must compensate, and it does the important part: it explains that `confirmed: true` represents a human's agreement, which is the semantic meaning of an otherwise opaque const boolean. `projectId` is only indirectly implied by 'one of your apps' — its UUID format and source are left to the schema.

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 uses a specific verb and resource ('Sign everyone out of one of your apps') and adds the consequence ('so they have to get in again'), which separates it in spirit from sibling access-management tools like appSharingRemovePeople. It stops short of naming any sibling, so the agent must infer the distinction rather than being told it.

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

Usage Guidelines3/5

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

Usage is implied by the effect described (all users must re-authenticate) and by the stated prerequisite of human agreement, which signals a deliberate, disruptive action. There is no explicit when-to-use or when-not-to-use guidance, and no routing to alternatives such as appSharingRemovePeople for removing a single person's access.

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