mcp-mistral-queue
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MISTRAL_API_KEY | Yes | Your Mistral API key |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_mistralA | Mistral APIをキューイングとレートリミット制御付きで呼び出します。 Args: ctx: MCP Context (自動で渡されます) prompt: 単発の入力プロンプトテキスト messages: 会話履歴オブジェクトの配列 ([{"role": "...", "content": "..."}]) model: 利用する Mistral モデル名 (default: mistral-small-latest) system_prompt: カスタムシステムプロンプト (prompt 指定時のみ有効) priority: タスク優先度 (1: 高, 2: 通常, 3: 低) Returns: Mistral API からのレスポンステキスト |
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 1 tool
Only one tool exists, so there is no possibility of ambiguity between tools.
With a single tool, naming is trivially consistent; the name 'ask_mistral' follows a clear verb_noun convention.
A single tool for a queue-based system feels too minimal; typical queue management would require additional tools for status checking or cancellation.
The tool covers only the submission aspect; missing queue status, priority management, and cancellation capabilities create significant gaps.