Skip to main content
Glama

Read app sign-in setup

appAuthStatus
Read-onlyIdempotent

Read one owned app’s sign-in configuration (Sign-in page): what its own auth service carries and what Tofu would write. It writes nothing and never returns the OAuth client secret. state is about that configuration, never about whether people can sign in; for not_configured and disabled, message says why (disabled: nothing about the app is affected). Sign-in through Tofu’s broker needs no per-app Google Cloud step, and consoleStep is always null: a person in appUsersList whose methods include google, with a lastSignInAt later than their attempt, has signed in with Google. message, except a static-hosted app’s refusal, ends by saying whether Tofu’s broker would start a Google sign-in for this app now. The result’s state distinguishes the observations: unavailable is not a configuration observation, and neither state nor consoleStep says whether sign-in works.

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>"
    },
    "name": "appAuthStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Output Schema

NameRequiredDescriptionDefault
stateYes
enabledYes
messageYes
siteUrlYes
nextStepsYes
providersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: it never returns the OAuth client secret, `consoleStep` is always null, no per-app Google Cloud step is needed, and `unavailable` is not a configuration observation. That is real disclosure beyond the annotations, though several sentences restate the read-only nature the annotations already assert.

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?

The description is a dense block of backtick-laden caveats with long, clause-heavy sentences ('a person in appUsersList whose `methods` include `google`, with a `lastSignInAt` later than their attempt, has signed in with Google'). The core purpose is stated first, but the remaining text is hard to parse and much of it duplicates what the output schema can express. Several qualifications could be tightened without loss.

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?

An output schema exists, so the extensive discussion of `state`, `message`, and `consoleStep` is largely redundant, while the required `projectId` and any prerequisites or sibling routing go unaddressed. The description is thorough about how to interpret the result but incomplete about how to call it and when to prefer it. It is adequate for a one-parameter read tool, with clear gaps.

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 0% for the single `projectId` parameter, so the description carries the burden — but it never mentions `projectId` or its UUID format. The only added meaning is the phrase 'one owned app,' which hints at an ownership/permission requirement. That is a thin compensation for an entirely undocumented required parameter.

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?

The description gives a specific verb and resource: 'Read one owned app's sign-in configuration (Sign-in page): what its own auth service carries and what Tofu would write.' An agent can tell this is a read of app-level auth config, and 'owned app' implies a scoping constraint. It never names a sibling such as appAuthConfigure or appAuthEmailStatus, so differentiation is left to inference.

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?

There is no explicit when-to-use or when-not-to-use statement, and no alternative is named. The closest thing to guidance is the caveat that `state` is 'never about whether people can sign in,' which warns against misreading the result but does not route the agent between tools. The agent must infer from the name and title alone that this is the inspection tool versus the configure tool.

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