Skip to main content
Glama

Remove people who can open an app

appSharingRemovePeople
DestructiveIdempotent

Remove people from the list of who can open one of your apps. 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>",
      "emails": "<emails>",
      "confirmed": "<confirmed>"
    },
    "name": "appSharingRemovePeople"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailsYes
confirmedYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
stateYes
messageYes
outcomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds the human-confirmation requirement, which is genuinely beyond the annotations, but it does not say what removal actually does to a person's live access, what happens for emails not on the list, or whether the operation is reversible.

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, zero filler, with the action front-loaded and the hard precondition second. Nothing repeats the title or the schema verbatim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the annotations cover the destructive/idempotent profile. Still, for a destructive, batch-capable tool with zero schema descriptions, the definition omits what the batch is keyed on and what the destructive effect actually entails, leaving meaningful gaps.

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 description coverage is 0%, so the description carries real weight here, and it explains `confirmed` well by tying it to human agreement. It says nothing about `projectId` (which app) or `emails` (batch semantics, the 1-50 cap, behavior on partial matches), leaving two of three parameters undocumented in both schema and prose.

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?

States a specific verb and resource: 'Remove people from the list of who can open one of your apps.' An agent can tell this is the inverse of appSharingAddPeople. It does not, however, distinguish itself from nearby siblings like appUsersRemove or appSharingSignOutEveryone, so the reader must infer that this edits the app's open-access list rather than the app's user roster.

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 only implied by the purpose statement; there is no explicit 'use this when X, not Y' guidance and no mention of when removal is the wrong lever (e.g., versus revoking an invite or signing a user out). The one concrete guideline given is the `confirmed: true` prerequisite, which is a precondition rather than a routing rule.

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