Skip to main content
Glama

Add app user

appUsersAdd
Idempotent

Add ONE email address as a person who can sign in to one owned app (Sign-in page) — the way in while sign-up is invited. Requires confirmed: true, representing the human’s agreement to add this exact address to this exact app; without the literal nothing is sent. Tofu creates their account in the app’s own sign-in service, confirmed and with no password: they sign in with Google, or with their email if the app offers that, and set a password with the app’s own “Forgot password” link if the app asks for one. Tofu sends no invitation or notification to the added person. already_there means the address already has an account and nothing was written, so repeating it is safe. If the app’s own sign-up step (one that creates a profile, say) turns the address away, the call fails and nobody is added. It never returns a password or a sign-in link. It doesn’t stop anyone opening the app; choosing who can open it is appSharingSetMode’s.

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>",
      "email": "<email>",
      "confirmed": "<confirmed>"
    },
    "name": "appUsersAdd"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes
confirmedYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
personYes
messageYes
outcomeYes
signupModeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only mark this as a non-read-only, idempotent, non-destructive write; the description goes well beyond that. It discloses that an account is created in the app's own sign-in service confirmed and with no password, that no invitation or notification is sent, that no password or sign-in link is ever returned, and that a rejecting app-level sign-up step causes the whole call to fail with nobody added.

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?

The critical constraint (one address, one app, confirmed required) is front-loaded and nearly every sentence adds distinct behavior. A few clauses are circuitous, notably "the way in while sign-up is `invited`", and the sign-in-method sentence could be tightened without losing information.

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 three-parameter write tool with an output schema, the description covers side effects, idempotency, failure semantics, and what is not returned, which is close to complete. The remaining gap is the unstated mapping of `projectId` to the target app, and the "Tofu" framing assumes product-name familiarity that the schema does not establish.

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 carry the load, and it does for `confirmed` — it explains the flag represents the human's agreement to add this exact address to this exact app, that it must be literally true, and that nothing is sent otherwise. `email` is constrained to ONE address with the sign-in meaning spelled out, but `projectId` is only implied via "one owned app" rather than named as the app identifier.

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?

"Add ONE email address as a person who can sign in to one owned app (Sign-in page)" gives a specific verb plus resource and explicit cardinality (one address, one app). It also distinguishes this from the sign-up path (`invited`) in the same sentence, so an agent can tell what this tool is not.

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

Usage Guidelines5/5

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

The description states the alternative path explicitly ("the way in while sign-up is `invited`") and disclaims a neighbouring responsibility: "It doesn't stop anyone opening the app; choosing who can open it is appSharingSetMode's." It also gives a retry rule — repeating an `already_there` result is safe — so the agent knows how to behave on subsequent calls.

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