Skip to main content
Glama

ai_modeling_auth_wait

Read-only

Waits briefly for a specified login flow to complete, then resume the original request or job after authentication instead of resubmitting an unknown outcome.

Instructions

Wait briefly for the specified login flow. This does not recheck current session availability. Resume the original request ID or job after authentication; never resubmit an unknown outcome.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "login_id": "<login_id>"
    },
    "name": "ai_modeling_auth_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
login_idYes
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.9/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: the call is a bounded block rather than a state recheck, and the 'never resubmit an unknown outcome' warning communicates a non-obvious idempotency hazard. It omits what the call returns or what happens when the wait times out, which are meaningful gaps for a blocking tool.

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?

Three short sentences, front-loaded with the action, then the exclusion, then the follow-up obligation. No filler and nothing repeated from the schema.

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?

For a two-parameter read-only wait tool this is close to sufficient, but with no output schema the description should say what the wait yields (auth result, pending state, or nothing) and what timeout behavior looks like. An agent can call it, but cannot fully predict the response.

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 carries only format and bounds (uuid pattern, default 30, min 1, max 60). The description ties login_id loosely to 'the specified login flow' but says nothing about timeout_seconds or what a short versus long wait changes, so it only partially compensates for the coverage gap.

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: 'Wait briefly for the specified login flow,' bounded by a login_id. It is distinguishable from a generic task wait, though it never names or contrasts with the nearby auth_status or task_wait siblings, leaving that differentiation to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear when-not ('This does not recheck current session availability'), which implicitly routes session checks elsewhere, plus explicit post-wait guidance to resume the original request or job. It stops short of naming the alternative tools or specifying when waiting is preferable to polling status.

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