Skip to main content
Glama

ai_modeling_auth_begin

Begins or reuses browser login for the active profile and returns a local login URL, enabling authentication without token input.

Instructions

Begin or reuse browser login for this profile. Returns a local login URL; no token input is required.

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_begin"
  }
}

Input Schema

NameRequiredDescriptionDefault
openNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.2/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, so the description does not need to re-establish that this touches the outside world. It usefully adds two behavioral facts the annotations cannot convey — the tool returns a local login URL and requires no token input — but it omits what happens after the URL is issued and whether a browser window is launched.

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?

Two short sentences with no filler, and the primary action is front-loaded. The second sentence earns its place by documenting the return value and the no-token requirement.

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 correctly explains what comes back (a local login URL). However, for an auth tool embedded in a multi-tool flow (begin, wait, status, cancel) it leaves the follow-up sequence and the meaning of the 'open' flag unexplained, leaving meaningful gaps.

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

Parameters2/5

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

The single parameter 'open' (boolean, default false) has 0% schema description coverage, and the description never mentions it. An agent cannot tell from either source whether 'open' launches a browser automatically versus only returning the URL, which is the key semantic decision for this tool.

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 states a specific verb and resource: 'Begin or reuse browser login for this profile.' 'Begin or reuse' also signals idempotency. It does not explicitly contrast itself with the adjacent auth_status/auth_wait/auth_cancel tools, so it stops just short of full sibling differentiation.

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: the agent can infer this is the entry point of the login flow and that calling it again reuses an existing session. There is no statement about when to prefer auth_wait, auth_status, or auth_cancel, and no preconditions are given.

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