Skip to main content
Glama
AtlasCloudAI

Atlas Cloud MCP Server (Image / Video / LLM APIs)

by AtlasCloudAI

Chat with LLM

atlas_chat

Send chat completion requests to LLM models using the Atlas Cloud API. Configure models, messages, and parameters to generate AI responses for various applications.

Instructions

Send a chat completion request to an LLM model via Atlas Cloud API (OpenAI-compatible format).

Args:

  • model (string, required): The LLM model ID (e.g., "deepseek-ai/deepseek-v3.2", "qwen/qwen3-32b")

  • messages (array, required): Array of message objects with "role" and "content" fields. Roles: "system", "user", "assistant"

  • temperature (number, optional): Sampling temperature, 0-2. Default: 1

  • max_tokens (number, optional): Maximum tokens in the response

  • top_p (number, optional): Nucleus sampling parameter, 0-1. Default: 1

Returns: The LLM response including the generated message, token usage, and finish reason.

Examples:

  • model="deepseek-ai/deepseek-v3.2", messages=[{"role": "user", "content": "Hello"}]

  • model="qwen/qwen3-32b", messages=[{"role": "system", "content": "You are a helpful assistant"}, {"role": "user", "content": "Explain quantum computing"}], temperature=0.7

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYesLLM model ID
messagesYesArray of chat messages
temperatureNoSampling temperature, 0-2. Default: 1
max_tokensNoMaximum tokens in the response
top_pNoNucleus sampling parameter, 0-1. Default: 1
Behavior4/5

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

Annotations provide basic hints (non-readOnly, non-destructive, non-idempotent, openWorld), but the description adds valuable context: it specifies the API format ('OpenAI-compatible'), mentions default values for temperature and top_p, and describes the return structure ('including generated message, token usage, finish reason'). This goes beyond what annotations convey about the tool's behavior.

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 well-structured with clear sections (purpose, Args, Returns, Examples), front-loading the core functionality. Every sentence earns its place by providing essential information without redundancy. The examples are concise yet illustrative of common use cases.

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?

For a tool with 5 parameters, 100% schema coverage, and no output schema, the description provides good context: it explains the API format, parameter defaults, and return structure. However, it doesn't mention potential errors, rate limits, or authentication requirements that would be helpful given the openWorldHint annotation. The examples help but don't fully compensate for missing output schema.

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?

With 100% schema description coverage, the input schema already documents all parameters thoroughly. The description provides examples that illustrate parameter usage but doesn't add significant semantic meaning beyond what's in the schema descriptions. The baseline of 3 is appropriate since the schema does the heavy lifting.

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?

The description clearly states the specific action ('Send a chat completion request') and resource ('to an LLM model via Atlas Cloud API'), with explicit format details ('OpenAI-compatible format'). It distinguishes this chat-focused tool from siblings like image/video generation or model listing tools by specifying its chat completion purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context through the OpenAI-compatible format mention and examples, but doesn't explicitly state when to use this tool versus alternatives like 'atlas_quick_generate' or 'atlas_get_prediction'. No guidance is provided about prerequisites, error conditions, or specific scenarios favoring this tool over siblings.

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/AtlasCloudAI/mcp-server'

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