Skip to main content
Glama

secure-flows

by io.github.michal-lefler

Log out (browser redirect helper; first-party cookie clearing)

get_auth_logout

Browser-friendly logout endpoint for cross-site clients (e.g. apps running on localhost).

Use this as a top-level navigation (not XHR/fetch) so Clear-Site-Data is applied in a first-party context on secure-flows.com, making cookie/session clearing reliable even when third-party cookies are blocked.

Critical client rules:

  • Clear your in-app sessionToken state before navigating.

  • Never include session_token inside redirect_uri (that would silently renew and defeat logout).

This endpoint (best-effort / idempotent for browser UX):

  • Invalidates the provided session_token by incrementing tokenRevision when the token still matches an active session (no new token is issued).

  • If the session is already expired/revoked or the revision was superseded by renew, still completes logout UX (does not return 401 solely for that reason).

  • Revokes Firebase refresh tokens for the session’s stored Firebase UID when known.

  • Sets Clear-Site-Data: "cookies".

  • Redirects the browser to redirect_uri.

Source: GET /api/v1/auth/logout No Authorization header is required. Prefer connection.workspaceName and connection.appId as stable config instead of generating identity fields dynamically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
authNo
bodyNo
queryYes
paramsNo
connectionYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: it is best-effort and idempotent, invalidates token via tokenRevision, handles already-expired sessions without 401, revokes Firebase tokens, sets Clear-Site-Data, and redirects. No behavioral aspect is left undisclosed.

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

Conciseness5/5

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

The description is detailed but well-structured with bullet points and clear sections (purpose, critical rules, behavior). Every sentence serves a purpose—no fluff. It is front-loaded with the primary purpose and usage constraint before behavioral details.

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

Completeness5/5

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

For a complex tool with nested input objects, zero annotations, and no output schema, the description covers all necessary context: endpoint source, client requirements, behavioral semantics, and redirect expectations. An agent can call it correctly without additional information.

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

Parameters5/5

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

Though the schema includes descriptions, the tool description goes further by relating session_token and redirect_uri to usage rules (e.g., never put token in redirect_uri). It adds critical context about what each parameter does in the logout flow, compensating for the low schema coverage signal.

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?

The description clearly states the tool's purpose: a browser-friendly logout endpoint for cross-site clients that invalidates a session token, clears cookies via Clear-Site-Data, and redirects. It differentiates itself from siblings by emphasizing the first-party baking context and navigation-only usage, making it distinct from post_auth_logout or URL builders.

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?

Explicitly directs use as top-level navigation, not XHR/fetch, and provides critical client rules (clear sessionToken before, never include session_token in redirect_uri). It also notes no Authorization header is required, and gives a preference for stable config fields, which guides the agent on when and how to call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All secure-flows toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools target distinct session/auth operations, and the descriptions clearly separate browser redirects from API endpoints. The main ambiguity is between get_sessions and get_sessions_my (payload vs. list) and the two logout variants, though the docs disambiguate them.

Naming Consistency4/5

API tools consistently use snake_case `{method}_{resource}_{action}` names, but a few deviate: `auth_session_callback` lacks the method prefix, `get_sessions_get_key`/`delete_sessions_delete_key` are redundant, and the `secureflows_*` helpers use a different prefix. Still readable and predictable.

Tool Count4/5

18 tools is slightly above the sweet spot, but the count is justified by distinct session lifecycle operations, auth redirects, and integration helpers. Only `get_docs_search` feels peripheral to the core session domain.

Completeness5/5

The surface covers session create, get-or-create, read, key-level update/delete, renew, revoke, logout, identity, and self-service listing/revocation, plus login/logout URL builders and linting. No important dead ends for the stated auth/session purpose.

Resources