Skip to main content
Glama
Sign In
chatgpt-webui-mcp

chatgpt-webui-mcp

by Microck
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

chatgpt_webui_session

Validate a ChatGPT session token to confirm its validity and retrieve session details for enabling web automation tasks.

Instructions

Validate ChatGPT session token and return session details.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

A3.5/5.0
Behavior2/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 indicates a read-only validation action, but does not disclose what happens with an invalid token, whether any side effects occur, or what 'session details' includes. This leaves behavioral ambiguity for the agent.

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?

A single, concise sentence that is front-loaded with the primary action and outcome. Every word contributes value, with no filler or redundant detail.

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 zero-parameter tool, the description is reasonably complete: it states the purpose and the return concept. However, it lacks usage timing, error behavior, and detail about what session details are returned, especially given there is no output schema to fill that gap.

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 tool has zero parameters and the schema is empty, so there is no parameter burden to document. The description's mention of a session token is contextually useful, though it is not a formal parameter. With 0 parameters, the baseline is appropriately high.

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 states a specific action ('Validate'), a clear resource ('ChatGPT session token'), and an expected outcome ('return session details'). This clearly distinguishes it from sibling tools like chatgpt_webui_ask or chatgpt_webui_models, which perform different operations.

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?

No guidance is given about when to use this tool versus the siblings. The description implies it could be used to check session validity before other operations, but it does not state this explicitly or provide any when-not-to-use conditions.

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