Skip to main content
Glama

ai_modeling_auth_status

Read-only

Reads a browser login-flow snapshot by login_id to match the original AUTH_REQUIRED response and inspect pending authentication status without rechecking credentials or the remote session.

Instructions

Read a browser login flow snapshot without checking current credentials or the remote session. Match login_id to the original AUTH_REQUIRED response.

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

Input Schema

NameRequiredDescriptionDefault
login_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, open-world, so safety is covered. The description adds real behavioral context beyond them: this returns a snapshot and deliberately does not re-check credentials or the remote session, warning the agent that the data may be stale. It does not describe the snapshot's contents or the staleness window, keeping it below a 5.

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?

Two short sentences, with the core action and its key constraint (snapshot, not live) front-loaded, followed by the parameter provenance. No filler and nothing redundant.

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

Completeness3/5

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

There is no output schema, so the description is the only place to describe what the snapshot contains (e.g., pending/authenticated/failed states) and it does not. For a status tool this is the main missing piece, though the precondition and staleness caveat are well covered.

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

Parameters3/5

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

Schema description coverage is 0%, so the schema alone gives only a UUID pattern with no meaning. The description partially compensates by explaining that login_id must be matched to the original AUTH_REQUIRED response, which conveys provenance. It does not explain what happens when the single optional parameter is omitted, leaving that ambiguity unresolved.

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: 'Read a browser login flow snapshot'. It also scopes itself with 'without checking current credentials or the remote session', which separates it from live status siblings like auth_wait/auth_status-style calls. It stops short of naming any sibling explicitly, so the differentiation is inferential 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?

'Match login_id to the original AUTH_REQUIRED response' implies the precondition for calling it (you have a login_id from a prior flow), which is useful implied usage. However, it never says when to prefer this over ai_modeling_auth_wait, ai_modeling_auth_cancel, or a live status check, and no exclusions are stated.

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

Deploy Server

Other Tools