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

chatgpt-webui-mcp

by Microck
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

chatgpt_webui_ask_async_result

Retrieve results from a background ChatGPT ask job by job ID, optionally waiting until complete.

Instructions

Get result for a background ask job. Optionally wait for completion by providing wait_timeout_ms.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_id": "<job_id>"
    },
    "name": "chatgpt_webui_ask_async_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob id returned by chatgpt_webui_ask_async_start.
wait_timeout_msNoOptional max wait for completion before returning current state.
poll_interval_msNoPolling interval while waiting. Default: 2000ms.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It mentions that waiting is optional but does not describe what happens when the job is incomplete, whether the call returns current state, or how polling behaves beyond the schema definitions.

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 and front-loaded, with no wasted words. It states the core purpose in one sentence and adds the key optional behavior in a short second clause.

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 three-parameter tool, the description covers the basic purpose and optional waiting behavior. However, with no output schema and no annotations, it omits useful context about what the result looks like and how incomplete jobs behave, so it is only minimally viable.

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%, so the schema already documents all parameters. The description adds a small amount of meaning by saying wait_timeout_ms waits for completion, but it does not go beyond what the schema already conveys.

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 clear action and resource: 'Get result for a background ask job.' It is specific enough for an agent to identify the tool's responsibility, though it does not explicitly contrast it with ask_async_status.

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 instead of ask_async_status or how it relates to ask_async_start. The only usage hint is the optional wait_timeout_ms, which is more about parameter behavior than tool selection.

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