Skip to main content
Glama
bunizao

okta-auth

by bunizao

okta_check_session

Read-onlyIdempotent

Verify an Okta session validity by checking a URL with stored cookies. Returns true if authenticated, false if redirected to login.

Instructions

Verify if a stored session for a URL is still valid.

Launches a headless browser with the stored session cookies, navigates to the URL, and checks whether the session is still authenticated (not redirected to Okta login).

Args: url: URL to verify session against. Must match the URL used during login. timeout_ms: Maximum time in ms to wait for page load (5000-120000, default 30000).

Returns: JSON: {"valid": bool, "domain_key": str|null, "message": str, "url": str}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
timeout_msNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Provides specific behavioral details beyond annotations: launches headless browser, uses cookies, checks for redirect. Annotations already indicate safe read operation; description enriches with mechanism.

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?

Concise yet comprehensive: states purpose, explains mechanism, lists arguments with details, specifies return format. No superfluous content.

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

Completeness4/5

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

Covers purpose, mechanism, parameters, and return format. Annotations provide safety profile. Could mention prerequisites (must have stored session from login) but implied. Good completeness for its complexity.

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?

Both parameters described with constraints and usage context. URL: must match login URL; timeout: range and default. Schema had no descriptions, so description fully compensates.

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?

States clear action: verify session validity for a URL. Distinguishes from sibling tools like login, list, delete, get cookies by focusing on validation. Includes specific method (headless browser, checking for redirect).

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?

Implies usage after login to verify session, but does not explicitly state when to use this tool over alternatives like okta_list_sessions. No exclusions or when-not guidance provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bunizao/okta-auth'

If you have feedback or need assistance with the MCP directory API, please join our Discord server