Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ROUTARA_API_KEYNoRoutara API key; optional for MCP discovery and required for tool calls
ROUTARA_API_BASENoBase URL for the Routara APIhttps://api.routara.ai/v1
ROUTARA_API_TIMEOUT_MSNoRequest timeout in milliseconds30000

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
routara_list_modelsA

List models available through Routara.

Use this before another tool when a model was not specified. Supports pagination and text filtering. The count field is always the total number of matches before pagination; returned is the number included in this response.

routara_chatA

Create an OpenAI-compatible chat completion through Routara.

Use message for a simple single-turn request, or messages for system prompts, multi-turn chat, multimodal content, and tool-call continuations. The complete upstream response is returned, including usage, reasoning_content, and tool_calls when supplied by the model.

routara_generate_imageB

Generate or edit an image through Routara.

Model support varies. Besides prompt and size, the tool can pass quality, aspect ratio, reference image URL, negative prompt, seed, style, and response format to compatible models.

routara_generate_videoA

Submit an asynchronous video-generation job through Routara.

Supports text-to-video and image-to-video. Save the returned id or task_id and poll it with routara_get_video_status until completed or failed.

routara_get_video_statusB

Poll a Routara video-generation job.

Pass the model when the upstream provider requires model-specific status routing.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct operation (listing models, chat, image generation, video submission, status polling) with no overlapping functionality. An agent can clearly distinguish between them.

Naming Consistency4/5

All tools are prefixed with 'routara_' and follow a verb_noun pattern (list_models, chat, generate_image, generate_video, get_video_status). The only minor inconsistency is 'chat' not using an underscore, but it remains clear.

Tool Count5/5

5 tools is an appropriate size for a server offering AI model interaction services. It is neither sparse nor overwhelming, covering the essential operations.

Completeness4/5

The set covers main workflows: listing models, chat completions, image generation, video submission, and status polling. A potential gap is lack of a cancel operation for video jobs, but core functionality is present.

Maintenance

ActivitySlowing
ResponsivenessNo issues