Skip to main content
Glama

overleaf_auth_status

Check Overleaf authentication status for Web Session cookies and Git Bridge tokens, optionally verifying live login validity to diagnose access or sync failures.

Instructions

Check Overleaf authentication status for both Web Session (cookies) and Git Bridge (token).

Args: verify_live: When True, tests the Web Session against Overleaf to confirm login validity.

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": "overleaf_auth_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
verify_liveNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It usefully explains that verify_live triggers a live test against Overleaf (i.e., a network call), but says nothing about side effects such as latency, rate limits, or whether a failed live check raises an error versus returning a status payload. The read-only nature is only implied by the verb 'Check'.

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?

One front-loaded sentence states the scope, followed by a compact Args block explaining the single parameter. No filler; the only minor inefficiency is the formal Args formatting for a single flag.

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?

An output schema exists, so return values need not be described. For a simple read-only status check with one boolean flag, the description covers what is checked, the two credential types, and the effect of the flag; only the failure/edge behavior is left implicit.

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?

Schema description coverage is 0%, but there is only one parameter and the description fully explains it: 'When True, tests the Web Session against Overleaf to confirm login validity,' including the default-implied consequence of skipping a live test. That meaning goes meaningfully beyond the bare boolean schema.

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 uses a specific verb and resource ('Check Overleaf authentication status') and even scopes it to both credential mechanisms (Web Session cookies and Git Bridge token), which no sibling name makes obvious. It does not explicitly contrast itself with overleaf_configure_auth, so it falls just short of a 5.

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 only implied: an agent can infer this is a pre-flight check before operations that need credentials, but there is no explicit 'use this when...' statement, no mention of when not to use it, and no reference to the configure_auth alternative. Adequate but leaves the routing decision to inference.

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