Model Advisor MCP
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recommend_modelB | Call at the START of a new task. Returns which Claude model (Haiku, Sonnet, Opus, Fable) fits the task best, so the user gets good results without wasting usage. Show the returned one_liner to the user. |
| review_model_choiceA | Call at the END of a substantial task. Says whether a lighter (or stronger) model would have been better next time. Show the returned note to the user only if change is 'up' or 'down'. |
| list_modelsA | Returns the model guide: each Claude model, its API id, and what it is best for. |
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 3 tools
Each tool occupies a distinct point in the task lifecycle: recommend_model at the start, review_model_choice at the end, and list_models as a static reference lookup. The descriptions explicitly state when to call each, leaving no realistic chance of misselection.
All three names follow the same verb_noun convention (recommend_model, review_model_choice, list_models) with snake_case throughout. The verbs are also semantically aligned with their described actions.
Three tools is on the lean side, but the domain is narrow (model selection advice) and each tool earns its place. Nothing feels padded or redundant.
The surface covers the advisory loop: reference guide, pre-task recommendation, and post-task review. Minor gaps exist, such as comparing two models head-to-head or retrieving past recommendations, but agents can work around these with list_models.