Skip to main content
Glama

secure-flows

by io.github.michal-lefler

Log out (invalidate sessionToken + revoke Firebase refresh tokens)

post_auth_logout

Logs out the current session without revoking it.

Browser warning: calling this endpoint via XHR/fetch from a different origin than secure-flows.com is not a reliable way to clear hosted-login cookies. For browser apps (especially localhost), prefer the redirect helper GET /api/v1/auth/logout?session_token=...&redirect_uri=....

Behavior:

  • Invalidates the current sessionToken by incrementing tokenRevision (no new token is issued).

  • Calls Firebase revokeRefreshTokens(firebaseUid) using the session’s stored Firebase UID.

  • Sets Clear-Site-Data: "cookies" to clear browser cookies (including Firebase session cookie).

Session payload and session row are not deleted or modified (other than tokenRevision).

Source: POST /api/v1/auth/logout Requires auth.sessionToken and forwards it as a Bearer token. Prefer connection.workspaceName and connection.appId as stable config instead of generating identity fields dynamically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
authNo
bodyNo
queryNo
paramsNo
connectionYes

Schema Changelog

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

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries full disclosure burden, and it delivers: it states tokenRevision increment, no new token issued, Firebase refresh-token revocation, Clear-Site-Data cookies, and that the session payload/row are not deleted. It also flags cross-origin limitations, which is valuable behavioral context.

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?

The description is front-loaded with a warning and then uses tight bullets for behavior, making the important side effects scannable. The opening 'without revoking' ambiguity and the trailing generic config sentence keep it from being fully sharp.

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 an auth mutation with no annotations and no output schema, the description covers the action, prerequisites, side effects, browser caveat, and preferred alternative. An agent has enough information to decide when to call it and what to expect.

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?

The description adds behavioral meaning not visible in the schema: auth.sessionToken is required and forwarded as a Bearer token, and connection.workspaceName/appId are recommended as stable config. It does not enumerate every parameter, but the remaining body/query/params are empty objects, so little is missing.

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 identifies a concrete action — logging out the current session — and names the counterpart GET redirect helper, so an agent can connect the tool to logout behavior. The opening phrase 'without revoking it' is ambiguous against the title's 'revoke Firebase refresh tokens' and the later revokeRefreshTokens bullet, which slightly muddies what exactly is and isn't revoked.

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?

It explicitly warns that XHR/fetch from a different origin is unreliable for clearing hosted-login cookies and directs browser apps, especially localhost, to the GET /api/v1/auth/logout redirect helper. This gives the agent a concrete condition for choosing an alternative.

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