mcp-ollama-account-rotation
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chatC | Send a chat completion request to Ollama |
| generateC | Generate text using Ollama |
| list_modelsB | List available models |
| get_account_statusA | Get current active account status |
| get_metricsC | Get server metrics |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Model List | List of available models |
| Current Account | Active account info |
| All Accounts | All accounts and their statuses |
TDQS
Scored across 5 tools
'chat' and 'generate' both involve text generation with overlapping functionality, making them hard to distinguish without additional context. The account-related tools (get_account_status, get_metrics) are distinct but mixed with unrelated generation tools, causing ambiguity about the server's core purpose.
Tool names use inconsistent patterns: 'chat' and 'generate' are single verbs, while 'list_models', 'get_account_status', and 'get_metrics' follow snake_case verb_noun. Mixing styles reduces predictability.
Five tools is a reasonable number, but the scope is muddled: only two tools (get_account_status, get_metrics) relate to the server's stated 'account rotation' purpose, while the others provide generic Ollama functionality, making the count feel imbalanced.
For an account rotation server, essential operations like switching accounts, listing accounts, or rotating keys are missing. The existing account tools are limited to status and metrics, leaving significant gaps that would hinder automation.