Skip to main content
Glama

Set who can sign up

appUsersSetSignupMode
Idempotent

Switch who can sign up to one owned app — “Who can sign up” on its Sign-in page. It changes the app for its visitors, and requires confirmed: true, representing the human’s agreement to this exact mode for this exact app; without the literal nothing is sent. mode: invited lets in only the people the owner added — anyone new who tries to sign up is turned away, on the app’s own sign-up page and through Tofu’s Google sign-in alike — and mode: anyone lets anyone sign up. Everyone who already has an account keeps signing in either way, and existing accounts are not removed by this change. It doesn’t stop anyone opening the app; choosing who can open it is appSharingSetMode’s. An error result alone does not establish the app’s current sign-up mode.

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>",
      "mode": "<mode>",
      "confirmed": "<confirmed>"
    },
    "name": "appUsersSetSignupMode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
confirmedYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
messageYes
outcomeYes
signupModeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is largely covered. The description adds genuinely useful behavioral context beyond that: existing accounts keep signing in and are not removed, the change applies to visitors on both the app's own sign-up page and Tofu's Google sign-in, the human-agreement confirmation gate, and the caveat that an error result alone does not establish the current mode. These extras are helpful but mostly restate scope rather than disclose failure/pagination/permission mechanics.

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?

Front-loaded with the action and scope before the details, and each sentence carries distinct information rather than filler. It is dense and long-ish with em-dash parentheticals, which slightly slows scanning, but nothing is redundant enough to cut outright.

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?

An output schema exists and annotations cover the safety profile, so the description's remaining burden is mode semantics, confirmation gating, and the sign-up-vs-access distinction — all present. The only shortfall is that the ownership/eligibility constraint behind projectId and the shape of a failure outcome are not fully spelled out.

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 meaning, and it does for two of three parameters: mode is defined precisely (invited = only people the owner added, anyone = open to all) and confirmed is explained as the human's agreement to this exact mode for this exact app, with the warning that nothing is sent without it. projectId is only implied by "one owned app" — no format or ownership constraint detail — leaving one parameter partly unaddressed.

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 ("Switch who can sign up to one owned app") and pins it to a UI location ("Who can sign up" on the Sign-in page). It explicitly contrasts with the sibling appSharingSetMode, so an agent can separate sign-up policy from access policy without opening either schema.

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?

Gives explicit when-to-use context and a named alternative: "It doesn't stop anyone opening the app; choosing who can open it is appSharingSetMode's." It also describes each mode's effect and states the preconditions (confirmed: true, one owned app), so the agent knows both when to call it and when not to.

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