Skip to main content
Glama

netintel_openai_gpt_5_4

Send OpenAI chat completion requests without an API key or account; pay $0.25 in USDC per call through an x402 endpoint.

Instructions

Call OpenAI's gpt-5.4 via a single pay-per-call x402 endpoint — no OpenAI account or API key needed, pay $0.25 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?

With no annotations, the description carries the full burden and does disclose meaningful traits: pay-per-call at $0.25 in USDC and no OpenAI account or API key required. It does not explain what the 'capped input and output' limits actually are, nor rate limits, error handling, or retry behavior.

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 sentence is front-loaded and reasonably tight, but it ends with an awkward truncated 'Search terms: OpenAI…' fragment that reads as keyword stuffing rather than useful 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?

For a paid, schema-sparse tool with no annotations and no output schema, the description covers the essential cost and auth story, but leaves the agent guessing about model selection, the nature of the input/output caps, and the response format beyond 'chat.completions shape'.

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 0%, so the schema documents neither parameter. The description partially compensates by stating that requests follow the 'standard OpenAI chat.completions request/response shape', which tells an agent what messages and max_completion_tokens mean, but it adds no explicit per-parameter detail.

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 — calling OpenAI's gpt-5.4 through an x402 pay-per-call endpoint — which is clearer than a bare name. However, amid a large cluster of near-identical siblings (gpt-5_5, gpt-5_4_mini, gpt-5_4_nano, gpt_4_1, v1_chat_completions), it gives no basis for choosing this specific model over the others.

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 never says when to pick gpt-5.4 versus the many other model siblings or netintel_openai. It offers payment/auth context (no key, $0.25 USDC) but no selection guidance or exclusions, so the agent is left to infer when this tool is appropriate.

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