Skip to main content
Glama
Sign In
mcp-chatgpt

mcp-chatgpt

by JonusNattapong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

chatgpt_login

Opens ChatGPT Web in a visible browser for manual login or CAPTCHA solving when automation needs user verification.

Instructions

Open ChatGPT Web in a visible (headed) browser window so the user can log in or solve Captcha challenges.

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

Input Schema

NameRequiredDescriptionDefault
profileNoOptional Chrome profile to log into.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It transparently notes the browser is visible, indicating user interaction, and mentions the specific actions (login/captcha). It does not mention potential side effects or return values, but these are likely minor.

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?

The description is concise, two sentences, and directly states the action and purpose. No redundant or ambiguous wording.

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?

Given the tool's simplicity and the lack of annotations/output schema, the description provides enough context: it opens a visible browser for authentication. It does not explain post-login behavior, but that is not essential for basic usage.

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?

The only parameter 'profile' is described as 'Optional Chrome profile to log into,' which adds meaning beyond the schema type (string). Since schema coverage is 100%, this description is sufficient and clear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: to open a visible browser window for logging in or solving captchas. It distinguishes this from sibling tools that handle chat, profiles, and queries.

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?

The description implies when to use (when user needs to log in or solve a captcha), but does not explicitly contrast with alternatives like chatgpt_ask or chatgpt_list_profiles. More explicit guidance would improve clarity.

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