GlianaAI MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GLIANA_RAIL | No | Payment rail: base, tempo, or solana | base |
| GLIANA_API_URL | No | API base URL | https://api.glianalabs.com |
| GLIANA_SOLANA_KEY | No | Private key (base58 or JSON array) for Solana rail. Needed for paid calls. | |
| GLIANA_WALLET_KEY | No | Private key (0x prefix) for Base or Tempo rail. Needed for paid calls. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_modelsA | List every GlianaAI model (id, category, provider, per-call price). Free — no payment. Use this to pick a model before get_price/generate. |
| get_priceA | Quote the exact cost of one call for a model (optionally with input that affects price, e.g. video duration or TTS character count). Free. |
| get_schemaA | Get a model’s input fields (names, types, which are required, defaults). Use before generate to know what to send. Free. |
| generateA | Run a model and return the result — a media URL for image/video/audio/music models, assistant text for text (LLM) models. Text models take OpenAI-style input: { messages: [{ role, content }, …], max_tokens? }. PAID: settles the price from your wallet over the configured rail (base/tempo/solana). Call get_schema first for the input shape, get_price for the cost. File inputs (image/video/audio, e.g. image-to-video or video-to-video |
| list_toolsA | List every GlianaAI utility tool (name, HTTP method, per-call price, an example input, and usage guidance), read live from the gateway so it is always current. Free — no payment. Call this before |
| toolA | Run a UTILITY tool (not an AI model) — scraping, screenshots, social cards, market data, chain RPC, OCR, address parsing, structured extraction, Indonesian reference data. Call list_tools FIRST for the live list with prices and input shapes: it is read from the gateway, so it is never out of date, and this description deliberately does not enumerate them. Most tools are PAID and settle a flat price from your wallet (base/tempo/solana); the ones list_tools reports at priceMicroUsd 0 are free and need no wallet at all. |
| recipeA | Run a paid multi-model RECIPE pipeline (chains models in one call). PAID: settles the SUM of the steps from your wallet (base/tempo/solana). Recipes: |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct concern: listing models vs. listing utility tools, pricing vs. schema vs. generation, and single-model generation vs. multi-model recipes. There is no meaningful overlap that would confuse an agent.
Most tools follow a verb_noun pattern (list_models, get_price, get_schema, list_tools), but 'generate' is verb-only and 'tool' and 'recipe' are bare nouns. The mix is readable but not uniformly consistent.
Seven tools is well-scoped for a server that covers both AI model access and utility tool execution. Each tool has a clear role without redundancy or bloat.
Core workflows (list, price, schema, generate, run utility, run recipe) are covered. However, file upload for media inputs is only available via an external HTTP endpoint, not an MCP tool, and there is no wallet management tool, leaving minor gaps.