model-version-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 |
|---|---|
| get_ai_modelsA | Returns current AI models (released within last 4 months) with pricing. Use this to get accurate, up-to-date model IDs instead of guessing. |
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
With only a single tool, there is no possibility of confusing it with another tool. The purpose of get_ai_models is clearly isolated and unambiguous.
The sole tool name follows a consistent verb_noun pattern (get_ai_models), which is clear and descriptive. There are no mixed conventions since only one name exists.
A single tool feels thin for an MCP server, even if the scope is narrowly focused on retrieving current AI models. While it can serve as a simple read-only utility, users might expect additional related operations given the server name.
The tool provides a core way to fetch recent AI models with pricing, but it lacks support for retrieving specific model details or older models outside the 4-month window. These gaps could force agents to work around the limitation or fail when needing historical model info.