Skip to main content
Glama

Read an app's user sign-in settings

app_users_get_settings
Read-only

The app's sign-in settings.

GET /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>"
    },
    "name": "app_users_get_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYes
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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds the multi-space prerequisite, which is genuinely useful behavior beyond annotations, but says nothing about authentication scope or what the returned settings actually contain.

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

Conciseness3/5

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

Very short and front-loaded, but the opening is a noun fragment with no verb, and restating the raw HTTP route in a tool description adds noise for an agent that already has the tool name and schema. The genuinely valuable content (space handling) is last.

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?

There is no output schema, so the description should say what the sign-in settings include (e.g., which auth methods or policies are returned), and it does not. With only two parameters and strong annotations, it is serviceable but leaves an agent unable to describe the result to a user before calling.

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 coverage is 50%, and the description's targetSpaceId guidance simply repeats the schema's own description verbatim in substance. appId gets no meaning beyond appearing in the URL template, so the description does not compensate for the undocumented half of the parameters. Baseline 3 is appropriate.

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?

Names the resource ('the app's sign-in settings') and the endpoint GET /api/v1/app-users/apps/{appId}/settings makes it unambiguous this is a read of per-app user sign-in settings. The read semantics come from the endpoint and the title rather than an explicit verb in the body, and it implicitly contrasts with app_users_put_settings, but it does not say how the returned settings differ from other 'settings' siblings.

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?

Gives a concrete procedural rule for multi-space accounts: call auth_verify, ask the user which space, then pass targetSpaceId. That is prerequisite handling rather than when-to-use-vs-alternative guidance; there is no statement about when not to use this tool or which sibling to prefer (e.g., put vs get).

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.