Skip to main content
Glama

ai_modeling_auth_cancel

Cancel an active browser login for a profile while preserving its saved Studio session. Use this to end a session without deleting stored account credentials.

Instructions

Cancel this profile's active browser login without deleting its saved Studio session.

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

Input Schema

NameRequiredDescriptionDefault
login_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world operation, so the safety profile is covered. The description adds genuine value by stating what is preserved (the saved Studio session), but it omits auth requirements, idempotency, and what happens when no active login exists.

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?

A single front-loaded sentence with the verb first and no filler; the preservation clause earns its place. It is efficient, though its brevity contributes to the parameter and usage gaps.

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 simple one-optional-parameter cancel tool with annotations covering safety, the core behavior and its non-destructive scope are conveyed. However, with no output schema the description should say what a successful cancel returns or how failures (no active login) surface, and the undocumented login_id remains a real gap.

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?

Schema description coverage is 0% for the single optional login_id parameter, and the description never explains what it targets. Worse, "this profile's active browser login" reads as profile-scoped, which leaves the role of login_id ambiguous rather than compensating for the schema 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?

"Cancel this profile's active browser login" gives a specific verb and resource, and the trailing clause ("without deleting its saved Studio session") meaningfully scopes it against other auth operations like begin/status/wait. It stops short of naming a sibling alternative, so it lands at 4 rather than 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no named alternative for the related auth tools. The intended usage is only implied by the verb and the preservation clause, leaving the agent to infer the triggering condition.

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