Skip to main content
Glama

netintel_openai_gpt_5_2

Send OpenAI chat completions through a pay-per-call x402 endpoint using USDC, bypassing the need for an OpenAI account or API key.

Instructions

Call OpenAI's gpt-5.2 via a single pay-per-call x402 endpoint — no OpenAI account or API key needed, pay $0.20 per request in USDC. Standard OpenAI chat.completions request/response shape, capped input and output. Search terms: OpenAI…

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messagesYes
max_completion_tokensNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.61

TDQS

B3.1/5.0
Behavior3/5

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

No annotations exist, so the description must carry behavioral disclosure. It does add genuinely useful context — pay-per-call x402 endpoint, $0.20 USDC per request, no OpenAI account/API key required — but fails to state output caps concretely, error behavior, or latency/rate characteristics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentences are efficient and front-load the key facts (model, payment, shape). However, the trailing 'Search terms: OpenAI…' fragment is a truncated, low-value tail that adds noise rather than information.

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?

With no output schema and no annotations, the description does cover the return shape by analogy to chat.completions and discloses the payment requirement. It still omits the actual input/output caps it advertises, leaving an agent without the constraints needed to call it safely.

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 0% and the schema is bare (messages as an undescribed array, max_completion_tokens with no docs). The reference to 'Standard OpenAI chat.completions request/response shape' partially compensates by telling the agent what messages should contain, but 'capped input and output' is too vague to explain max_completion_tokens limits.

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 specific verb and resource (call OpenAI's gpt-5.2 chat completion) and uniquely identifies the model among a large family of sibling model endpoints. It does not, however, explain how it differs in purpose from netintel_openai_gpt_5_1, gpt_4_1, or netintel_v1_chat_completions beyond the model label.

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?

The description gives no when-to-use guidance and no comparison against the ~15 sibling model endpoints, which is exactly what an agent needs to choose among gpt-5.2, gpt-5.1, gpt-5-nano, etc. Pricing is mentioned but that is not selection guidance for the task at hand.

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