Skip to main content
Glama

Add people who can open an app

appSharingAddPeople
Idempotent

Add people by email to the list of who can open one of your apps. Tofu doesn’t email them: send them the link yourself. This doesn’t make the app private and isn’t the app’s own sign-up. Requires confirmed: true, representing the human’s agreement to add these people to this app.

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": "appSharingAddPeople"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailsYes
confirmedYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
stateYes
messageYes
outcomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a non-read-only, idempotent, non-destructive, open-world write. The description adds real context beyond them: no email is sent, the human must relay the link, app privacy is unchanged, and the `confirmed` flag encodes a human-agreement gate. Missing only permission requirements (who may call it) and duplicate-handling behavior, which idempotentHint only hints at.

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?

Four short sentences, all load-bearing: the action first, then the non-emailing caveat, then the two scope exclusions, then the requirement. No padding or repetition.

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?

Output schema exists, so return values need no description. For a 3-param mutation with a human-confirmation gate, the guidance on what it does and doesn't do is nearly complete; only caller permissions and behavior on already-listed emails are unaddressed.

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 must compensate. It does well on `confirmed` (explicitly the human's agreement, matching the const:true) and implies `emails` are addresses, but never mentions the 1–50 item cap or clarifies that `projectId` identifies 'one of your apps'. Partial compensation, so a mid score.

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: 'Add people by email to the list of who can open one of your apps.' It also carves out scope against neighboring concepts ('doesn't make the app private and isn't the app's own sign-up'), so an agent can tell it apart from the sharing-mode and signup tools without opening a 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?

Gives clear context and implicit exclusions: it neither sends invites nor changes privacy, and it isn't signup, which steers an agent away from using it for those jobs. It stops short of naming the sibling to use instead (e.g., the invite or signup-mode tools), so a small inference remains.

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