Skip to main content
Glama

auth_status

Read-only

Check whether a saved Overleaf web session is still valid and when it expires, without exposing cookies.

Instructions

Verify the saved Overleaf web session without exposing cookies. sessionExpiresAt is when the session lapses unless a request refreshes it first; Overleaf sessions last five days from their last use, and the CLI command overleaf-web-mcp keepalive can be scheduled to refresh them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "auth_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
userIdNo
baseUrlYes
warningNo
projectCountYes
authenticatedYes
sessionExpiresAtNo
permissionsUncheckedYes
socketPresenceNoticeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description goes further by promising cookies are never exposed and by explaining how sessionExpiresAt is computed (five days from last use, refreshed by any request). The mention of a schedulable keepalive command adds operational context an agent cannot get from annotations.

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 purpose is front-loaded in the first sentence and the expiry mechanics follow as supporting detail. The second sentence is dense, packing expiry, lifetime, and a CLI workaround together, but each clause carries distinct information.

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 zero-parameter read with an output schema and readOnlyHint already covering safety and returns, this description supplies everything else an agent needs: what is verified, what is not leaked, and how long the session remains valid.

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?

With zero parameters, the baseline is 4. The description still adds meaning by interpreting the returned sessionExpiresAt field, which is beyond what the empty input schema can convey.

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?

States a specific verb and resource: 'Verify the saved Overleaf web session,' plus the constraint 'without exposing cookies.' That distinguishes it from a mutating auth flow, but it never names the sibling it contrasts with (sign_in), so the differentiation is implicit rather than explicit.

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?

Usage is implied rather than stated: an agent can infer this is a pre-flight validity check, and the keepalive hint suggests what to do when the session lapses. It never says when to call this instead of sign_in, or what to do when verification fails, so the guidance stops short of explicit routing.

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