Skip to main content
Glama
Sign In
Polydev

Polydev

Official
by polydev-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Continue with ChatGPT

connect_chatgpt_plan

Start ChatGPT sign-in so OpenAI models queried through ask_model use your own ChatGPT plan. Returns the sign-in link immediately; check the status afterwards.

Instructions

Continue with ChatGPT: start ChatGPT sign-in so that OpenAI models asked through ask_model use your ChatGPT plan. Returns the sign-in link right away (it also tries to open the browser); call chatgpt_plan_status afterwards for the result. The sign-in and its tokens stay on this machine.

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

Input Schema

NameRequiredDescriptionDefault
timeout_secondsNoHow long the sign-in stays open (default 300)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Goes beyond the annotations: it discloses that the call returns the sign-in link immediately rather than blocking for the whole flow, that it may also pop a browser, and that credentials/tokens remain on the local machine (a useful privacy signal). It does not say what a returned link looks like or what happens if the timeout elapses unused, which are the remaining gaps given openWorldHint=true.

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 tight sentences, front-loaded with the action and purpose, then the return behavior, then the required next step. Nothing is repeated from the title and no sentence is filler.

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?

For a non-destructive, open-world auth-initiation tool with a single well-documented parameter and no output schema, the description covers purpose, immediate return value, and the mandatory follow-up call. Missing only the relationship to the `login` sibling and the failure/expiry behavior, which would fully close the loop.

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 coverage is 100% and the single timeout_seconds parameter is fully documented in the schema (default 300, range 30-600). The description adds no additional meaning about that timeout, so the schema does all the work — baseline 3.

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?

States a specific verb and resource ("start ChatGPT sign-in") plus the concrete downstream effect: OpenAI models queried through ask_model will use the user's ChatGPT plan. This clearly separates it from sibling tools like chatgpt_plan_status (status check) and login (generic auth), so an agent can pick correctly without reading schemas.

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 trigger (when you want ask_model to use the ChatGPT plan) and an explicit follow-up step ("call chatgpt_plan_status afterwards for the result"). It stops short of distinguishing this from the sibling `login` tool, leaving a real ambiguity about which auth entry point to choose.

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