Skip to main content
Glama

Turn app user sign-in on or off

app_users_put_settings

The saved settings.

PUT /api/v1/app-users/apps/{appId}/settings

For multi-space accounts, call auth_verify, ask the user which space to use, and pass targetSpaceId.

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": {
      "appId": "<appId>",
      "enabled": "<enabled>"
    },
    "name": "app_users_put_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYes
appNameNo
enabledYes
targetSpaceIdNoBusabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is partly covered. The description adds a genuine behavioral step the annotations do not: for multi-space accounts the agent must call auth_verify and confirm the space before writing. It still omits what the write actually replaces (whether existing settings are overwritten or merged) and the sentence "The saved settings." is ambiguous enough to be misread as a return value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is brief, but the first sentence is wasted (and misleading), and the second is a bare HTTP path rather than an explanation, so the definition is not front-loaded with purpose. The only substantive content, the multi-space flow, arrives last with no lead-in.

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

Completeness2/5

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

For a non-destructive mutation with four parameters, 25% schema coverage, and no output schema, the definition leaves the essential facts unstated: what the enabled flag controls, whether appName is used, and what effect the call has on saved settings. Only the space-selection workflow is adequately covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, so the description must compensate, and it largely does not: appId, appName, and enabled are unaddressed, and there is no statement of what enabled=true versus false does or whether appName is optional metadata. The targetSpaceId guidance repeats almost verbatim the description already present in the schema property.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with "The saved settings.", which restates the resource in the name rather than stating an action. The raw path PUT /api/v1/app-users/apps/{appId}/settings implies a write, but the description never says it turns app-user sign-in on or off — only the title carries that meaning, and the description does not differentiate it from siblings like app_users_enable/disable or app_users_get_settings.

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

Usage Guidelines2/5

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

The only guidance given is a multi-space prerequisite (call auth_verify, ask the user, pass targetSpaceId), which is about parameter sourcing rather than when to choose this tool. Nothing says when to use this PUT versus app_users_enable, app_users_disable, or app_users_get_settings, nor what preconditions exist.

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.