Skip to main content
Glama
yuz0101

@gammainfra/mcp-server

by yuz0101

chat_completions

Send chat completion requests with smart routing. Choose a model or let the router pick, then get the response and routing metadata.

Instructions

Send a chat completion request to GammaInfra and receive the model response plus routing metadata. Smart routing picks the best-fit model when model='gammainfra/auto'; pin a specific model like 'openai/gpt-5-mini' for direct dispatch. Returns the OpenAI-shape response in a 'response' field and routing decisions (provider, endpoint, cost in USD, router version, fallback chain) in a 'routing_meta' field. Streaming is not supported via MCP; the request always uses stream=false.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYesModel name. Use 'gammainfra/auto' to let the router pick, 'gammainfra/fast' for latency, 'gammainfra/cheap' for cost, or pin a specific provider/model like 'openai/gpt-5-mini' or 'anthropic/claude-opus-4-7'.
toolsNo
top_pNo
regionNoConstrain endpoint region: 'us', 'eu', 'apac', or specific AWS region like 'us-east-1'. Sent as X-GammaInfra-Region header.
messagesYesConversation messages in OpenAI shape.
max_tokensNo
preferenceNoCoarse routing preference. Sent as X-GammaInfra-Preference header.
temperatureNo
tool_choiceNo
cost_qualityNoContinuous cost-vs-quality dial. 0.0 = pure quality, 1.0 = pure cost. Sent as X-GammaInfra-Cost-Quality header.
max_latency_msNoCap total wall-clock time (including fallback retries) in ms. Sent as X-GammaInfra-Max-Latency-Ms header.
response_formatNo
presence_penaltyNo
frequency_penaltyNo
max_completion_tokensNo
Behavior4/5

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

Without annotations, the description proactively discloses key behaviors: smart routing vs direct dispatch, the return format (response + routing_meta fields), and streaming unsupported. It could mention error or rate limit behavior, but the provided info is substantial and non-contradictory.

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 concise (3 sentences) and front-loaded with the core action. Every sentence adds value without redundancy, making it efficient for an agent to parse.

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

Completeness2/5

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

Given 15 parameters and no output schema or annotations, the description only covers the core functionality and response structure. It fails to explain advanced routing features (preference, cost_quality, max_latency) and other common parameters needed for effective use.

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

Parameters2/5

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

With schema description coverage at only 40%, many parameters lack explanations. The description only clarifies the 'model' parameter and implicitly sets stream=false. It does not explain parameters like tools, temperature, cost_quality, or max_latency_ms, leaving a significant gap for the agent.

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 verb 'Send a chat completion request' and the resource 'to GammaInfra' with specific routing logic for model selection. It distinguishes from sibling tools (get_status, list_models, get_balance) which serve different purposes.

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?

The description explains when to use 'gammainfra/auto' vs pinning a specific model, and explicitly notes that streaming is not supported via MCP. However, it does not provide explicit alternative tools for streaming or when not to use this tool.

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

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