Skip to main content
Glama

Ask ChatGPT

ask_chatgpt
Read-only

This tool allows you to send a prompt to OpenAI's ChatGPT via ScrapingBee and get back the generated response.

Scope: one query per call. To run many queries in one pass, or to write results to disk instead of into the conversation, use the ScrapingBee CLI — scrapingbee <command> --input-file queries.txt --output-dir results.

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": {
      "prompt": "<prompt>"
    },
    "name": "ask_chatgpt"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoResponse-header label only.
promptYesThe prompt to send to ChatGPT.
searchNoWhether to enable web search capability for the prompt.
add_htmlNoWhether to include the full HTML of the page in the results.
country_codeNoISO country code the request should originate from (affects web results when search is enabled).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true is consistent with a prompt-and-response operation, so no contradiction exists. The description adds useful context beyond the annotations—the request is proxied through ScrapingBee and the call accepts a single prompt—but says nothing about latency, cost, rate limits, or failure modes of the scraping layer.

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?

Two short, front-loaded blocks: what it does, then the scope/batch limitation with a CLI example. The command example is slightly verbose but earns its place by making the escaping route concrete.

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?

With a full output schema, five well-documented parameters, and a read-only annotation, the description supplies what is missing: the proxying mechanism and the single-query scope. Only operational details (latency, quota consumption) are absent, which is a minor gap for a tool this simple.

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 description coverage is 100%, so all five parameters (including the non-obvious 'tag', 'search', 'add_html', and 'country_code') are already explained in the schema. The description adds only the one-query-per-call constraint and no extra meaning for individual parameters, so the baseline of 3 applies.

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?

States a concrete verb pair and resource: 'send a prompt to OpenAI's ChatGPT via ScrapingBee and get back the generated response.' Naming the underlying model implicitly separates it from the ask_gemini sibling, but the description never explicitly contrasts the two, so differentiation is inferred rather than stated.

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?

Explicitly scopes the tool to 'one query per call' and routes batch work or file output to the ScrapingBee CLI with a concrete invocation example. It gives a clear when-not/alternative, though it offers no guidance on choosing between this and ask_gemini or the direct search tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources