Skip to main content
Glama

chat_completion

Send chat completion requests to DeepSeek V4 Flash via proxy. Provide messages in OpenAI format to receive AI responses with token usage and cost estimates.

Instructions

Send a chat completion request to DeepSeek V4 Flash through the GadgetHumans proxy. REQUIRES an API key with credits. Get one via wallet_create or wallet_buy.

Use this to get AI responses. Each call costs ~1 credit from your wallet.
Accepts an OpenAI-compatible messages format. Returns response with
content, token usage, and cost estimate.

Parameters:
    messages    — JSON string of messages array (e.g. '[{"role":"user","content":"Hello"}]').
                  Must be valid JSON with at least one message.
    model       — Model to use (default: "deepseek-v4-flash").
    temperature — Sampling temperature (0.0-1.0, default: 0.7).
    max_tokens  — Maximum tokens in response (default: 2000).
    api_key     — Your wallet API key (starts with 'gh_'). REQUIRED for paid access.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messagesYes
modelNodeepseek-v4-flash
temperatureNo
max_tokensNo
api_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses cost (~1 credit per call) and return value contents (content, token usage, cost). Does not mention error handling or rate limits, which would improve transparency.

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?

Concise and well-structured: purpose, prerequisites, usage, then parameter details in bullet-like format. Every sentence adds value; no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 5 parameters, output schema exists, and no annotations, the description covers purpose, prerequisites, cost, parameter details, and return value hints. It is sufficiently complete for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, description adds crucial details: messages must be valid JSON array string with at least one message, model default and options, temperature range, max_tokens default, and api_key format requirement. Greatly enhances understanding.

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?

Description clearly states the tool sends a chat completion request to a specific model (DeepSeek V4 Flash) through a proxy. This distinguishes it from sibling tools like 'summarize' or 'translate' which are different AI tasks.

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 states when to use ('get AI responses') and prerequisites (API key with credits, obtained via wallet_create or wallet_buy). Does not mention alternatives, but siblings don't compete directly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scotia1973-bot/api-hub'

If you have feedback or need assistance with the MCP directory API, please join our Discord server