370.ai — AI Gateway: Video (Seedance 2.0, Wan, HappyHorse), Image, Speech + 100+ Chat Models

chat

Ask any text/chat model on 370.ai (Claude / GPT / Gemini / DeepSeek / Qwen / ...) and get its reply.

Use this when you want a **specific or different** model than your own — e.g. consult Claude while you run on
GPT, use a cheaper model for bulk work, or reach a model you don't have direct access to. One key, 100+ models.
Call list_models to see the full catalog of model ids.

Args:
    prompt: the user message / question.
    model: model id to call (see list_models). Empty = a fast cheap default.
    system: optional system instruction to steer the model.
    max_tokens: optional cap on output length (omit to let the model decide).
    temperature: optional sampling temperature 0..2 (omit for the model's default).
Returns the model's text reply.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`model`	No
`prompt`	Yes
`system`	No
`max_tokens`	No
`temperature`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJun 10, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description bears the full burden. It tells the agent that the tool returns the model's text reply, describes the 'model' default as 'fast cheap default', and explains parameter effects. However, it does not disclose potential costs, rate limits, or any side effects beyond the reply. There is no contradiction with annotations (none exist), but transparency is only partial.

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 front-loaded with the core purpose, followed by concise guidance and a neatly tabulated Args list. No filler or redundant sentences; every line earns its place. The structure is highly readable and aids an agent's quick parsing.

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 chat tool with 5 parameters, the description covers purpose, usage scenarios, parameter semantics, and the return value ('Returns the model's text reply'). It also references list_models for the full model catalog, and the existence of an output schema reduces the need to detail return format. Missing error-case or rate-limit info, but the essentials are sufficiently covered.

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

Parameters4/5

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

The schema has no parameter descriptions (0% coverage), so the description compensates well. It explains each argument: prompt is 'the user message / question', model is a 'model id' with empty meaning 'fast cheap default', system is 'optional system instruction', max_tokens is 'optional cap on output length', and temperature is '0..2'. This adds meaning beyond the bare schema types and defaults.

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 tool's function: 'Ask any text/chat model on 370.ai ... and get its reply.' It explicitly names the resource (models on 370.ai) and the action (ask/get reply), and distinguishes it from sibling tools like generate_image or text_to_speech.

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?

Provides explicit use cases: 'when you want a specific or different model than your own', gives concrete examples (consult Claude while on GPT, cheaper model for bulk work), and points to list_models for the catalog. Lacks an explicit 'when not to use' but the alternative is implied through list_models.

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

All 370.ai — AI Gateway: Video (Seedance 2.0, Wan, HappyHorse), Image, Speech + 100+ Chat Models tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct capability—chat completion, image generation, text-to-speech, and model discovery—so an agent can clearly choose by modality. There is no overlap or ambiguity between the four tools.

Naming Consistency4/5

generate_image and list_models follow a clear verb_noun pattern, while chat and text_to_speech deviate slightly. The names are still readable and generally action-oriented, but the conventions are not fully uniform.

Tool Count4/5

Four tools is lean but reasonable for a broad multimodal gateway, as each tool covers a major capability and list_models supports discovery across 100+ models. The count feels slightly thin given the advertised video and speech scope, but there is no redundant tool weight.

Completeness2/5

The server name prominently advertises video generation with Seedance, Wan, and HappyHorse, yet no video generation tool is exposed. Image is limited to generation and speech is limited to text-to-speech, leaving significant gaps for a supposed multimodal video/image/speech/chat gateway.

Resources

Need Help?